fix npm-module docs

Author: thheller

docs/UsersGuide.html

@@ -3482,39 +3482,28 @@ <h3 id="_explicit_configuration"><a class="anchor" href="#_explicit_configuratio
 </tr>
 <tr>
 <td class="hdlist1">
-<code>:entries</code>
+<code>:output-dir</code>
 </td>
 <td class="hdlist2">
-<p>(optional) A vector of namespaces to include. Everything from these will be included.
-Defaults to everything it can find.</p>
+<p>The path for supporting files in development mode.</p>
 </td>
 </tr>
 <tr>
 <td class="hdlist1">
-<code>:output-dir</code>
+<code>:entries</code>
 </td>
 <td class="hdlist2">
-<p>(optional). The path for supporting files in development mode. Defaults to
-<code>node_modules/shadow-cljs</code>.</p>
+<p>(optional) A vector of namespaces to include. Everything from these will be included.
+Defaults to everything it can find.</p>
 </td>
 </tr>
 </table>
 </div>
 <div class="paragraph">
-<p>The <code>:entries</code> setting can be used to limit what things get included, and the <code>:output-dir</code> is
-particularly useful for naming the directory in <code>node_modules</code> so that you can
-customize what name you use with <code>require</code>.</p>
-</div>
-<div class="paragraph">
-<p>Each entry will still result in a file with that namespace name in the specified output directory.</p>
-</div>
-<div class="paragraph">
-<p>Of course all of this is generated with standard Node conventions.</p>
+<p>If you use an <code>:output-dir</code> like <code>"node_modules/shadow-cljs"</code> you can access them by using <code>require("shadow-cljs/demo.foo")</code>. When using something not in <code>node_modules</code> you must include them using a relative path. With <code>:output-dir "out"</code> that would be <code>require("./out/demo.foo")</code> from your project root.</p>
 </div>
 <div class="paragraph">
-<p>If you plan to distribute code on NPM, then you may want to use the
-<a href="#NodeLibrary"><code>:node-library</code> target</a> instead since it allows for a finer level of control
-over exports and optimization.</p>
+<p>If you plan to distribute code on NPM, then you may want to use the <a href="#NodeLibrary"><code>:node-library</code> target</a> instead since it allows for a finer level of control over exports and optimization.</p>
 </div>
 </div>
 <div class="sect2">

docs/target-npm-module.adoc

@@ -52,22 +52,14 @@ options are:
 
 [horizontal]
 `:target`:: Use :npm-module
+`:output-dir`:: The path for supporting files in development mode.
 `:entries`:: (optional) A vector of namespaces to include. Everything from these will be included.
 Defaults to everything it can find.
-`:output-dir`:: (optional). The path for supporting files in development mode. Defaults to
-`node_modules/shadow-cljs`.
 
-The `:entries` setting can be used to limit what things get included, and the `:output-dir` is
-particularly useful for naming the directory in `node_modules` so that you can
-customize what name you use with `require`.
 
-Each entry will still result in a file with that namespace name in the specified output directory.
+If you use an `:output-dir` like `"node_modules/shadow-cljs"` you can access them by using `require("shadow-cljs/demo.foo")`. When using something not in `node_modules` you must include them using a relative path. With `:output-dir "out"` that would be `require("./out/demo.foo")` from your project root.
 
-Of course all of this is generated with standard Node conventions.
-
-If you plan to distribute code on NPM, then you may want to use the
-<<NodeLibrary, `:node-library` target>> instead since it allows for a finer level of control
-over exports and optimization.
+If you plan to distribute code on NPM, then you may want to use the <<NodeLibrary, `:node-library` target>> instead since it allows for a finer level of control over exports and optimization.
 
 == Working with Optimizations