indentation

brucejo75 · Sep 4, 2011 · 30d9838 · 30d9838
1 parent df8c465
commit 30d9838
Show file tree

Hide file tree

Showing 3 changed files with 31 additions and 13 deletions.
diff --git a/doc/removing-npm.md b/doc/removing-npm.md
@@ -24,18 +24,18 @@ you configured node with a different `--prefix`, or installed npm with a
 different prefix setting, then adjust the paths accordingly, replacing
 `/usr/local` with your install prefix.
 
-   rm -rf /usr/local/{lib/node,lib/node/.npm,bin,share/man}/npm*
+    rm -rf /usr/local/{lib/node,lib/node/.npm,bin,share/man}/npm*
 
 If you installed things *with* npm, then your best bet is to uninstall
 them with npm first, and then install them again once you have a
 proper install.  This can help find any symlinks that are lying
 around:
 
-   ls -laF /usr/local/{lib/node,lib/node/.npm,bin,share/man} | grep npm
+    ls -laF /usr/local/{lib/node,lib/node/.npm,bin,share/man} | grep npm
 
 Prior to version 0.3, npm used shim files for executables and node
 modules.  To track those down, you can do the following:
 
-   find /usr/local/{lib/node,bin} -exec grep -l npm \{\} \; ;
+    find /usr/local/{lib/node,bin} -exec grep -l npm \{\} \; ;
 
 (This is also in the README file.)
diff --git a/html/doc/removing-npm.html b/html/doc/removing-npm.html
@@ -362,19 +362,19 @@ <h2 id="More-Severe-Uninstalling">More Severe Uninstalling</h2>
 different prefix setting, then adjust the paths accordingly, replacing
 <code>/usr/local</code> with your install prefix.</p>
 
-<p>   rm -rf /usr/local/{lib/node,lib/node/.npm,bin,share/man}/npm*</p>
+<pre><code>rm -rf /usr/local/{lib/node,lib/node/.npm,bin,share/man}/npm*</code></pre>
 
 <p>If you installed things <em>with</em> npm, then your best bet is to uninstall
 them with npm first, and then install them again once you have a
 proper install.  This can help find any symlinks that are lying
 around:</p>
 
-<p>   ls -laF /usr/local/{lib/node,lib/node/.npm,bin,share/man} | grep npm</p>
+<pre><code>ls -laF /usr/local/{lib/node,lib/node/.npm,bin,share/man} | grep npm</code></pre>
 
 <p>Prior to version 0.3, npm used shim files for executables and node
 modules.  To track those down, you can do the following:</p>
 
-<p>   find /usr/local/{lib/node,bin} -exec grep -l npm {} \; ;</p>
+<pre><code>find /usr/local/{lib/node,bin} -exec grep -l npm \{\} \; ;</code></pre>
 
 <p>(This is also in the README file.)</p>
 </div>
@@ -406,4 +406,4 @@ <h2 id="More-Severe-Uninstalling">More Severe Uninstalling</h2>
 
 </script>
 </body></html>
-<!-- npm help removing-npm - 2011-11-04 08:09:47 -->
+<!-- npm help removing-npm - 2011-35-04 08:09:30 -->
diff --git a/man1/removing-npm.1 b/man1/removing-npm.1
@@ -43,24 +43,42 @@ This assumes that you installed node and npm in the default place\.  If
 you configured node with a different \fB\-\-prefix\fR, or installed npm with a
 different prefix setting, then adjust the paths accordingly, replacing \fB/usr/local\fR with your install prefix\.
 .
-.P
-   rm \-rf /usr/local/{lib/node,lib/node/\.npm,bin,share/man}/npm*
+.IP "" 4
+.
+.nf
+rm \-rf /usr/local/{lib/node,lib/node/\.npm,bin,share/man}/npm*
+.
+.fi
+.
+.IP "" 0
 .
 .P
 If you installed things \fIwith\fR npm, then your best bet is to uninstall
 them with npm first, and then install them again once you have a
 proper install\.  This can help find any symlinks that are lying
 around:
 .
-.P
-   ls \-laF /usr/local/{lib/node,lib/node/\.npm,bin,share/man} | grep npm
+.IP "" 4
+.
+.nf
+ls \-laF /usr/local/{lib/node,lib/node/\.npm,bin,share/man} | grep npm
+.
+.fi
+.
+.IP "" 0
 .
 .P
 Prior to version 0\.3, npm used shim files for executables and node
 modules\.  To track those down, you can do the following:
 .
-.P
-   find /usr/local/{lib/node,bin} \-exec grep \-l npm {} \\; ;
+.IP "" 4
+.
+.nf
+find /usr/local/{lib/node,bin} \-exec grep \-l npm \\{\\} \\; ;
+.
+.fi
+.
+.IP "" 0
 .
 .P
 (This is also in the README file\.)