diff --git a/source_control/git b/source_control/git
index d6bfb554e31..213cccb0c7a 100644
--- a/source_control/git
+++ b/source_control/git
@@ -82,10 +82,10 @@ options:
             - Path to git executable to use. If not supplied,
               the normal mechanism for resolving binary paths will be used.
 notes:
-    - If the task seems to be hanging, first verify remote host is in C(known_hosts).
+    - "If the task seems to be hanging, first verify remote host is in C(known_hosts).
       SSH will prompt user to authorize the first contact with a remote host.  To avoid this prompt, 
       one solution is to add the remote host public key in C(/etc/ssh/ssh_known_hosts) before calling 
-      the git module, with the following command: ssh-keyscan remote_host.com >> /etc/ssh/ssh_known_hosts.
+      the git module, with the following command: ssh-keyscan remote_host.com >> /etc/ssh/ssh_known_hosts."
 '''
 
 EXAMPLES = '''
diff --git a/source_control/hg b/source_control/hg
index 6da2e5675d9..5293ed3d27e 100644
--- a/source_control/hg
+++ b/source_control/hg
@@ -73,10 +73,10 @@ options:
             - Path to hg executable to use. If not supplied,
               the normal mechanism for resolving binary paths will be used.
 notes:
-    - If the task seems to be hanging, first verify remote host is in C(known_hosts).
+    - "If the task seems to be hanging, first verify remote host is in C(known_hosts).
       SSH will prompt user to authorize the first contact with a remote host.  To avoid this prompt, 
       one solution is to add the remote host public key in C(/etc/ssh/ssh_known_hosts) before calling 
-      the hg module, with the following command: ssh-keyscan remote_host.com >> /etc/ssh/ssh_known_hosts.
+      the hg module, with the following command: ssh-keyscan remote_host.com >> /etc/ssh/ssh_known_hosts."
 requirements: [ ]
 '''