diff options
| author | Daniel J Walsh <dwalsh@redhat.com> | 2018-12-21 10:27:54 -0500 |
|---|---|---|
| committer | Daniel J Walsh <dwalsh@redhat.com> | 2018-12-21 10:27:54 -0500 |
| commit | 4d1326240501312d60bce184db7f63d9e5cfae49 (patch) | |
| tree | 8ca70973a38611a9c9850c05c0ffc55f18b56a60 /README.md | |
| parent | 664076c259c8751483fbcbe57ab5273d9f3e5c8c (diff) | |
| download | podman-4d1326240501312d60bce184db7f63d9e5cfae49.tar.gz podman-4d1326240501312d60bce184db7f63d9e5cfae49.tar.bz2 podman-4d1326240501312d60bce184db7f63d9e5cfae49.zip | |
Change all 'can not' to 'cannot' for proper usage
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -106,7 +106,7 @@ to be long lived. While Buildah containers are really just created to allow con to be added back to the container image. An easy way to think of it is the `buildah run` command emulates the RUN command in a Dockerfile while the `podman run` command emulates the `docker run` command in functionality. Because of this and their underlying -storage differences, you can not see Podman containers from within Buildah or vice versa. +storage differences, you cannot see Podman containers from within Buildah or vice versa. In short Buildah is an efficient way to create OCI images while Podman allows you to manage and maintain those images and containers in a production environment using |