update order in which we search for various files (jsdoc#162)

hegemonic · hegemonic · commit 60664fa09a71 · 2017-07-09T16:58:16.000-07:00
diff --git a/about-configuring-default-template.html b/about-configuring-default-template.html
@@ -95,7 +95,7 @@ <h2 id="overriding-the-default-template-s-layout-file">Overriding the default te
       this file defines which CSS and JavaScript files are loaded for each page. In JSDoc 3.3.0 and later, you can specify your own <code>layout.tmpl</code> file
       to use, which allows you to load your own custom CSS and JavaScript files in addition to, or instead of, the standard files.</p>
     <p>To use this feature, set the option <code>templates.default.layoutFile</code> to the path to your customized layout file. Relative paths are resolved against
-      the path to the configuration file; the current working directory; and the JSDoc directory, in that order.</p>
+      the current working directory; the path to the configuration file; and the JSDoc directory, in that order.</p>
     <h2 id="related-links">Related Links</h2>
     <p>
       <a href="about-configuring-jsdoc.html">Configuring JSDoc with a configuration file</a>
diff --git a/about-plugins.html b/about-plugins.html
@@ -50,8 +50,8 @@ <h2 id="creating-and-enabling-a-plugin">Creating and Enabling a Plugin</h2>
     <ol>
       <li>Create a JavaScript module to contain your plugin code.</li>
       <li>Include that module in the <code>plugins</code> array of <a href="about-configuring-jsdoc.html">JSDoc&#39;s configuration file</a>. You can specify an absolute
-        or relative path. If you use a relative path, JSDoc searches for the plugin in the directory where the configuration file is located; the current working
-        directory; and the JSDoc directory, in that order.</li>
+        or relative path. If you use a relative path, JSDoc searches for the plugin in the current working directory; the directory where the configuration file
+        is located; and the JSDoc directory, in that order.</li>
     </ol>
     <p>For example, if your plugin is defined in the <code>plugins/shout.js</code> file in the current working directory, you would add the string <code>plugins/shout</code>      to the <code>plugins</code> array in your JSDoc configuration file:</p>
     <figure>
diff --git a/content/en/about-configuring-default-template.md b/content/en/about-configuring-default-template.md
@@ -90,5 +90,5 @@ use, which allows you to load your own custom CSS and JavaScript files in additi
 of, the standard files.
 
 To use this feature, set the option `templates.default.layoutFile` to the path to your customized
-layout file. Relative paths are resolved against the path to the configuration file; the current
-working directory; and the JSDoc directory, in that order.
+layout file. Relative paths are resolved against the current working directory; the path to the
+configuration file; and the JSDoc directory, in that order.
diff --git a/content/en/about-plugins.md b/content/en/about-plugins.md
@@ -10,7 +10,7 @@ There are two steps required to create and enable a new JSDoc plugin:
 1. Create a JavaScript module to contain your plugin code.
 2. Include that module in the `plugins` array of [JSDoc's configuration file][config-file]. You can
 specify an absolute or relative path. If you use a relative path, JSDoc searches for the plugin in
-the directory where the configuration file is located; the current working directory; and the JSDoc
+the current working directory; the directory where the configuration file is located; and the JSDoc
 directory, in that order.
 
 For example, if your plugin is defined in the `plugins/shout.js` file in the current working
