diff --git a/site/operational-guide/autoscaling.md b/site/operational-guide/autoscaling.md
index 79a0db40..7bb79d1b 100644
--- a/site/operational-guide/autoscaling.md
+++ b/site/operational-guide/autoscaling.md
@@ -39,7 +39,7 @@ You do not have to keep track of and specify the addresses
 of other dynamic peers in `$PEERS` - they will discover and connect to
 each other via the fixed cluster.
 
->>**Note:** The use of `--ipalloc-init=observer` prevents dynamic peers from
+>**Note:** The use of `--ipalloc-init=observer` prevents dynamic peers from
 coming to a consensus on their own - this is important to stop a
 clique forming amongst a group of dynamically added peers if they
 become partitioned from the fixed cluster after having learned about
diff --git a/site/operational-guide/tasks.md b/site/operational-guide/tasks.md
index 3c703b97..d8375f0a 100644
--- a/site/operational-guide/tasks.md
+++ b/site/operational-guide/tasks.md
@@ -99,7 +99,7 @@ To minimize downtime while the new script is pulling the new container images:
 * Start the new Weave Net with `weave launch <existing peer list>` (or
   `systemctl start weave` if you're using a systemd unit file)
 
->>**Note:** Always check the Release Notes for specific versions in case
+>**Note:** Always check the Release Notes for specific versions in case
 there are any special caveats or deviations from the standard
 procedure.
 
diff --git a/site/operational-guide/uniform-fixed-cluster.md b/site/operational-guide/uniform-fixed-cluster.md
index fa9c56d4..04a3d9ef 100644
--- a/site/operational-guide/uniform-fixed-cluster.md
+++ b/site/operational-guide/uniform-fixed-cluster.md
@@ -42,7 +42,7 @@ Then on _any_ peer run the following to force consensus:
 
     weave prime
 
->>**Note:** You can run this safely on more than one or
+>**Note:** You can run this safely on more than one or
 even all peers, but it's only strictly necessary to run it on one of
 them.