diff --git a/docs/src/snap/howto/upgrades.md b/docs/src/snap/howto/upgrades.md
index b8209e02c..859d25cf7 100644
--- a/docs/src/snap/howto/upgrades.md
+++ b/docs/src/snap/howto/upgrades.md
@@ -3,8 +3,8 @@
 Upgrading the Kubernetes version of a node is a critical operation that 
 requires careful planning and execution. {{product}} is shipped as a snap,
 which simplifies the upgrade process.
-This how-to guide will cover the steps to upgrade the {{product}} snap to a 
-new version as well as how to freeze upgrades.
+This how-to guide will cover the steps to upgrade the {{product}} snap 
+and how to put a hold on upgrades if desired.
 
 ## Important Considerations Before Upgrading
 
@@ -20,10 +20,9 @@ This can be done by following the steps outlined in the [backup guide][3].
 
 Patch upgrades address bug fixes and are typically safe, introducing no 
 breaking changes.
-{{product}} snap is installed using a specific track (e.g. `1.32-classic`). 
-Snaps automatically check for updates several times a day and apply 
-them when available.
-These updates ensure the latest changes in the installed track are applied.
+Snaps automatically check for updates of their specific track 
+(e.g. `1.32-classic`) several times a day and apply them when available.
+These updates ensure that the latest changes in the installed track are applied.
 Patch upgrades can also be triggered manually by following the steps below.
 
 1. **List available revisions:**
@@ -77,9 +76,9 @@ In a multi-node cluster, the upgrade should be performed on all nodes.
 
 ## Freezing Upgrades
 
-To prevent automatic updates, the snap can be frozen to a specific revision. 
-`snap refresh --hold[=<duration>]` holds refreshes for a specified duration 
-(or forever, if no value is specified).
+To prevent automatic updates, the snap can be tied to a specific revision. 
+`snap refresh --hold[=<duration>]` holds snap refreshes for a specified 
+duration (or forever, if no value is specified).
 ```
 snap refresh k8s --hold
 ```