Skip to content

Commit 9c5eb8d

Browse files
committed
fix typo
1 parent f147966 commit 9c5eb8d

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/how-to/upgrade/minor-rollback.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ After running `juju refresh`, if there are any version incompatibilities in char
55
Even if the underlying PostgreSQL cluster continues to work, it’s important to roll back the charm to the {term}`original version` so that an update can be attempted after further inspection of the failure.
66

77
```{attention}
8-
Only trigger a rollback if the refresh has expicitly failed and cannot continue. Do not initiate a rollback while the refresh process is still running.
8+
Only trigger a rollback if the refresh has explicitly failed and cannot continue. Do not initiate a rollback while the refresh process is still running.
99
1010
<!--TODO: examples-->
1111
```

docs/how-to/upgrade/minor-upgrade.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ Units will be refreshed one by one based on role: first the `replica` units, the
7777
If there are any version incompatibilities in charm revisions, dependencies, or any other unexpected failure in the upgrade process, the process will halt and enter a failure state.
7878

7979
```{attention}
80-
Only trigger a rollback if the refresh has expicitly failed and cannot continue. <!--TODO: examples + clarify if you can rollback when refresh is healthy but paused waiting for resume-refresh -->
80+
Only trigger a rollback if the refresh has explicitly failed and cannot continue. <!--TODO: examples + clarify if you can rollback when refresh is healthy but paused waiting for resume-refresh -->
8181
```
8282

8383
## Resume refresh

0 commit comments

Comments
 (0)