add some small clarifications

Author: a-velasco

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

@@ -14,7 +14,7 @@ Only trigger a rollback if the refresh has explicitly failed and cannot continue
 
 ## Initiate rollback
 
-Perform a rollback with the command obtained from the [pre-refresh check](pre-refresh check) that was performed before initiating the refresh process.
+Perform a rollback with the command obtained from the [pre-refresh check](pre-refresh check) that was performed before initiating the refresh process. You can also find it in the [Juju logs](https://documentation.ubuntu.com/juju/3.6/howto/manage-logs/#view-the-log-files).
 
 <!--TODO: example-->
 

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

@@ -44,7 +44,9 @@ This will ensure minimal service disruption, if any.
 (pre-refresh-check)=
 ## Pre-refresh check
 
-The `pre-refresh-check` action will check that a refresh is possible and will switch the primary, if necessary, for a safe upgrade process. 
+The `pre-refresh-check` action checks that a refresh is possible and will switch the primary, if necessary, for a safe upgrade process.
+
+This check happens automatically when you run `juju refresh`, but we recommend running it manually before scheduling a maintenance window for the refresh operation.
 
 Run a pre-refresh check against the leader unit: