addressed feedback

Author: sarahsanders-docker

docs/reference/buildx_history_export.md

@@ -41,12 +41,10 @@ To export two builds to separate files:
 
 ```console
 # Using build IDs
-docker buildx history export qu2gsuo8ejqrwdfii23xkkckt -o mybuild.dockerbuild
-docker buildx history export qsiifiuf1ad9pa9qvppc0z1l3 -o backend-build.dockerbuild
+docker buildx history export qu2gsuo8ejqrwdfii23xkkckt qsiifiuf1ad9pa9qvppc0z1l3 -o multi.dockerbuild
 
 # Or using relative offsets
-docker buildx history export ^1 -o mybuild.dockerbuild
-docker buildx history export ^2 -o backend-build.dockerbuild
+docker buildx history export ^1 ^2 -o multi.dockerbuild
 ```
 
 Or use shell redirection:

docs/reference/buildx_history_logs.md

@@ -63,13 +63,3 @@ $ docker buildx history logs ^1 --progress rawjson
 {"id":"buildx_step_1","status":"COMPLETE","timestamp":"2024-05-01T12:34:57.001Z","duration":212000000}
 ...
 ```
-
-### <a name="print-logs-tty"></a> Print logs in TTY format
-
-```console
-# Using a build ID
-docker buildx history logs qu2gsuo8ejqrwdfii23xkkckt --progress tty
-
-# Or using a relative offset
-docker buildx history logs ^1 --progress tty
-```

docs/reference/buildx_history_trace.md

@@ -59,10 +59,10 @@ Compare two specific builds by name:
 
 ```console
 # Using build IDs
-docker buildx history trace --compare qu2gsuo8ejqrwdfii23xkkckt qsiifiuf1ad9pa9qvppc0z1l3
+docker buildx history trace --compare=qu2gsuo8ejqrwdfii23xkkckt qsiifiuf1ad9pa9qvppc0z1l3
 
 # Or using a single relative offset
-docker buildx history trace --compare ^1
+docker buildx history trace --compare=^1
 ```
 
 When you use a single reference with `--compare`, it compares that build