doc/toolbox-enter, doc/toolbox-run: Fix the custom container examples
When a specific Toolbx container is selected by name for 'enter' and 'run', it's not necessary that the container was created using a custom image. The container could have also been created using one of the built-in images. Secondly, the phrase 'using a custom image' is awkward because it makes it sound as if the image plays an important role in 'enter' and 'run'. That's not true. Finally, titles are sweeter when they are shorter. https://github.com/containers/toolbox/pull/1281 Signed-off-by: Nils Lindemann <nilslindemann@tutanota.com>
This commit is contained in:
parent
198107cceb
commit
cceea52af6
2 changed files with 2 additions and 2 deletions
|
@ -54,7 +54,7 @@ $ toolbox enter
|
|||
$ toolbox enter --distro fedora --release f36
|
||||
```
|
||||
|
||||
### Enter a custom toolbox container using a custom image
|
||||
### Enter a toolbox container with a custom name
|
||||
|
||||
```
|
||||
$ toolbox enter foo
|
||||
|
|
|
@ -97,7 +97,7 @@ $ toolbox run ls -la
|
|||
$ toolbox run --distro fedora --release f36 emacs
|
||||
```
|
||||
|
||||
### Run uptime inside a custom toolbox container using a custom image
|
||||
### Run uptime inside a toolbox container with a custom name
|
||||
|
||||
```
|
||||
$ toolbox run --container foo uptime
|
||||
|
|
Loading…
Reference in a new issue