diff --git a/source/release-notes/2.4-upgrade.txt b/source/release-notes/2.4-upgrade.txt
index 0b9354f0555..366c6fa0397 100644
--- a/source/release-notes/2.4-upgrade.txt
+++ b/source/release-notes/2.4-upgrade.txt
@@ -143,21 +143,21 @@ procedure.
       processes, you may connect to a 2.2 :program:`mongos` process
       and force the lock manually:
 
-   .. code-block:: sh
+      .. code-block:: sh
 
-      mongo <mongos.example.net>
+         mongo <mongos.example.net>
 
-   .. code-block:: javascript
-
-      db.getMongo().getCollection("config.locks").findOne({ _id : "upgradeLock" })
+      .. code-block:: javascript
+   
+         db.getMongo().getCollection("config.locks").findOne({ _id : "upgradeLock" })
 
       If the process specified in the ``process`` field of this document
       is *verifiably* offline, run the following operation to force the
       lock.
 
-   .. code-block:: javascript
+      .. code-block:: javascript
 
-      db.getMongo().getCollection("config.locks").update({ _id : "upgradeLock" }, { $set : { state : 0 } })
+         db.getMongo().getCollection("config.locks").update({ _id : "upgradeLock" }, { $set : { state : 0 } })
 
       It is always more safe to wait for the :program:`mongos` to verify
       that the lock is inactive, if you have any doubts about the