reword

Signed-off-by: Antheas Kapenekakis <[email protected]>

docs/src/bootc-via-api.md

@@ -53,13 +53,14 @@ and removing old images.
 
 You could show a different progress bar for each step or have a unified
 one with a fixed ratio for each stage. For a unified progress bar, depending
-on your application and image size, you may use `70/15/15` or `80/10/10`.
-To achieve this, you can hard-code a ratio for each `task` field in the
-schema. Importing and staging are affected by disk speed and the total image 
-size. Pulling is affected by network speed and how many layers invalidate 
-between pulls. Therefore, a large image with a good caching strategy will
-have longer importing and staging times, and a small bespoke container
-image will have negligible importing and staging times.
+on your application and image size, you may use a ratio `70/15/15` or 
+`80/10/10` for the stages. To implement it in practive, you can hard-code 
+a starting place and width for each `task` field in the schema. Importing
+and staging are affected by disk speed and the total image size. Pulling 
+is affected by network speed and how many layers invalidate between pulls. 
+Therefore, a large image with a good caching strategy will have longer 
+importing and staging times, and a small bespoke container image will have 
+negligible importing and staging times.
 
 ## Using `bootc edit`