diff --git a/CMakeLists.txt b/CMakeLists.txt
old mode 100644
new mode 100755
diff --git a/source/Commands/CommandObjectCommands.cpp b/source/Commands/CommandObjectCommands.cpp
old mode 100644
new mode 100755
index 6824ead..8b085cf
--- a/source/Commands/CommandObjectCommands.cpp
+++ b/source/Commands/CommandObjectCommands.cpp
@@ -450,13 +450,15 @@ public:
                                          // 'bp delete'. \n\
     'command alias bpl breakpoint list'  // Creates the abbreviation 'bpl' for the \n\
                                          // two-word command 'breakpoint list'. \n\
-    \nAn alias can include some options for the command, with the values either \n\
+    \n\
+    An alias can include some options for the command, with the values either \n\
     filled in at the time the alias is created, or specified as positional \n\
     arguments, to be filled in when the alias is invoked.  The following example \n\
     shows how to create aliases with options: \n\
     \n\
     'command alias bfl breakpoint set -f %1 -l %2' \n\
-    \nThis creates the abbreviation 'bfl' (for break-file-line), with the -f and -l \n\
+    \n\
+    This creates the abbreviation 'bfl' (for break-file-line), with the -f and -l \n\
     options already part of the alias.  So if the user wants to set a breakpoint \n\
     by file and line without explicitly having to use the -f and -l options, the \n\
     user can now use 'bfl' instead.  The '%1' and '%2' are positional placeholders \n\
@@ -474,24 +476,30 @@ public:
     \n\
     to get the file extension \".cpp\" automatically appended.  For more complex\n\
     aliasing, use the \"command regex\" command instead.\n\
-    \nSo in the 'bfl' case, the actual file value will be \n\
+    \n\
+    So in the 'bfl' case, the actual file value will be \n\
     filled in with the first argument following 'bfl' and the actual line number \n\
     value will be filled in with the second argument.  The user would use this \n\
     alias as follows: \n\
     \n    (lldb)  command alias bfl breakpoint set -f %1 -l %2 \n\
     <... some time later ...> \n\
     (lldb)  bfl my-file.c 137 \n\
-    \nThis would be the same as if the user had entered \n\
+    \n\
+    This would be the same as if the user had entered \n\
     'breakpoint set -f my-file.c -l 137'. \n\
-    \nAnother example: \n\
-    \n    (lldb)  command alias pltty  process launch -s -o %1 -e %1 \n\
+    \n\
+    Another example: \n\
+    \n\
+    (lldb)  command alias pltty  process launch -s -o %1 -e %1 \n\
     (lldb)  pltty /dev/tty0 \n\
            // becomes 'process launch -s -o /dev/tty0 -e /dev/tty0' \n\
-    \nIf the user always wanted to pass the same value to a particular option, the \n\
+    \n\
+    If the user always wanted to pass the same value to a particular option, the \n\
     alias could be defined with that value directly in the alias as a constant, \n\
     rather than using a positional placeholder: \n\
-    \n    command alias bl3  breakpoint set -f %1 -l 3  // Always sets a breakpoint on line \n\
-                                                   // 3 of whatever file is indicated. \n");
+    \n\
+    command alias bl3  breakpoint set -f %1 -l 3  // Always sets a breakpoint on line \n\
+                                                  // 3 of whatever file is indicated. \n");
 
         CommandArgumentEntry arg1;
         CommandArgumentEntry arg2;