diff options
| author | tomsweeneyredhat <tsweeney@redhat.com> | 2022-05-26 15:45:40 -0400 |
|---|---|---|
| committer | tomsweeneyredhat <tsweeney@redhat.com> | 2022-05-26 16:15:07 -0400 |
| commit | 3a32d60e5bb215f2c6b1b9a22b68134687b09370 (patch) | |
| tree | a9e8dc41202c14f91f449b0c99e3a424cbbf9cf6 | |
| parent | 1736f2fe607a82d066497aba330d6a81a07f5164 (diff) | |
| download | podman-3a32d60e5bb215f2c6b1b9a22b68134687b09370.tar.gz podman-3a32d60e5bb215f2c6b1b9a22b68134687b09370.tar.bz2 podman-3a32d60e5bb215f2c6b1b9a22b68134687b09370.zip | |
[CI:DOCS] Quick typo for troubleshooting
After lgtming the latest from @flouthouc, I spotted one
more minor typo in the troubleshooting guide. This corrects it.
Signed-off-by: tomsweeneyredhat <tsweeney@redhat.com>
| -rw-r--r-- | troubleshooting.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/troubleshooting.md b/troubleshooting.md index 6e7f5cf26..4be925f71 100644 --- a/troubleshooting.md +++ b/troubleshooting.md @@ -1230,4 +1230,4 @@ While running podman remote commands with the most updated Podman, issues that w When upgrading Podman to a particular version for the required fixes, users often make the mistake of only upgrading the Podman client. However, suppose a setup uses `podman-remote` or uses a client that communicates with the Podman server on a remote machine via the REST API. In that case, it is required to upgrade both the Podman client and the Podman server running on the remote machine. Both the Podman client and server must be upgraded to the same version. -Example: If a particular bug was fixed in `v4.1.0` then The Podman client` must have version `v4.1.0` as well the Podman server must have version `v4.1.0`. +Example: If a particular bug was fixed in `v4.1.0` then the Podman client must have version `v4.1.0` as well the Podman server must have version `v4.1.0`. |