diff --git a/lib/ansible/modules/extras/windows/win_dotnet_ngen.py b/lib/ansible/modules/extras/windows/win_dotnet_ngen.py
index 5f6d45062d..90f464a1b0 100644
--- a/lib/ansible/modules/extras/windows/win_dotnet_ngen.py
+++ b/lib/ansible/modules/extras/windows/win_dotnet_ngen.py
@@ -31,9 +31,10 @@ description:
     - This happens via scheduled task, usually at some inopportune time.
     - This module allows you to run this task on your own schedule, so you incur the CPU hit at some more convenient and controlled time.
     - "http://blogs.msdn.com/b/dotnet/archive/2013/08/06/wondering-why-mscorsvw-exe-has-high-cpu-usage-you-can-speed-it-up.aspx"
-    - "Note: there are in fact two scheduled tasks for ngen but they have no triggers so aren't a problem"
-    - "Note: there's no way to test if they've been completed (?)"
-    - Note: the stdout is quite likely to be several megabytes
+notes:
+    - there are in fact two scheduled tasks for ngen but they have no triggers so aren't a problem
+    - there's no way to test if they've been completed (?)
+    - the stdout is quite likely to be several megabytes
 options:
 author: Peter Mounce
 '''