diff --git a/conf.py b/conf.py
index 78474346168..2ffba3e5437 100644
--- a/conf.py
+++ b/conf.py
@@ -76,7 +76,7 @@ def has(self, *args):
     'meta-driver': ('http://docs.mongodb.org/meta-driver/latest%s', ''),
     'mms-docs': ('https://docs.cloud.mongodb.com%s', ''),
     'mms-home': ('https://cloud.mongodb.com%s', ''),
-    'opsmgr': ('https://docs.opsmanager.mongodb.com%s', ''),
+    'opsmgr': ('https://docs.opsmanager.mongodb.com/current/%s', ''),
     'about': ('https://www.mongodb.org/about%s', ''),
     'products': ('https://www.mongodb.com/products%s', '')
 }
diff --git a/source/includes/steps-restore-primary-from-backup.yaml b/source/includes/steps-restore-primary-from-backup.yaml
index 9b7a78f707e..2547dacc9f4 100644
--- a/source/includes/steps-restore-primary-from-backup.yaml
+++ b/source/includes/steps-restore-primary-from-backup.yaml
@@ -8,9 +8,9 @@ content: |
   produces MongoDB database files for :mms-docs:`stored snapshots
   </tutorial/restore-from-snapshot/>` and :mms-docs:`point in time
   snapshots </tutorial/restore-from-point-in-time-snapshot/>`.
-  For an :products:`Ops Manager, an on-premise solution available in
+  For :products:`Ops Manager, an on-premise solution available in
   MongoDB Enterprise Advanced </mongodb-enterprise-advanced?jmp=docs>`,
-  see also :opsmgr:`documentation on Backup </core/backup-overview>`.
+  see also the :opsmgr:`Ops Manager Backup overview </core/backup-overview>`.
 
   You
   can also use :program:`mongorestore` to restore database files using
diff --git a/source/tutorial/enable-authentication-in-sharded-cluster.txt b/source/tutorial/enable-authentication-in-sharded-cluster.txt
index aae4b4fe459..e17f10d79ae 100644
--- a/source/tutorial/enable-authentication-in-sharded-cluster.txt
+++ b/source/tutorial/enable-authentication-in-sharded-cluster.txt
@@ -21,7 +21,7 @@ enabling authentication on each :program:`mongos` and each
 of a shard's replica set.
 
 Authentication requires an authentication mechanism and, in most cases, a
-:setting:`key file <keyFile>`. The content of the key file must be the
+:setting:`keyfile <keyFile>`. The content of the key file must be the
 same on all cluster members.
 
 Considerations