Typo fixup for #961

Signed-off-by: John Eckersberg <jeckersb@redhat.com>

docs/src/experimental-progress-fd.md

@@ -6,7 +6,7 @@ This is an experimental feature; tracking issue: <https://github.com/containers/
 While the `bootc status` tooling allows a client to discover the state
 of the system, during interactive changes such as `bootc upgrade`
 or `bootc switch` it is possible to monitor the status of downloads
-or other operations at a fine-grained level with `-progress-fd`.
+or other operations at a fine-grained level with `--progress-fd`.
 
 The format of data output over `--progress-fd` is [JSON Lines](https://jsonlines.org)
 which is a series of JSON objects separated by newlines (the intermediate
@@ -29,4 +29,4 @@ Importing and staging are affected by disk speed and the total image size. Pulli
 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.
+negligible importing and staging times.

lib/src/progress_jsonl.rs

@@ -227,7 +227,7 @@ impl ProgressWriter {
         }
 
         // For messages that can be dropped, if we already sent an update within this cycle, discard this one.
-        // TODO: Also consider querying the pipe buffer and also dropping if wqe can't do this write.
+        // TODO: Also consider querying the pipe buffer and also dropping if we can't do this write.
         let now = Instant::now();
         if !required {
             const REFRESH_MS: u32 = 1000 / REFRESH_HZ as u32;