From ec203ba577198f4b071d0f23cc2a0c4982a46529 Mon Sep 17 00:00:00 2001
From: Philip Peitsch <philip.peitsch@gmail.com>
Date: Tue, 29 Jan 2013 22:43:16 +1100
Subject: [PATCH 1/5] All line endings within an article are now normalized to
 be \n

---
 Jakefile.js | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Jakefile.js b/Jakefile.js
index 2569c125..5cd5bd54 100644
--- a/Jakefile.js
+++ b/Jakefile.js
@@ -50,7 +50,7 @@ task('default', [], function (params) {
     console.log('Building new gh-pages...');
     
     articles.forEach(function (article) {
-        var html = Mustache.to_html(
+        var html = convertEOL(Mustache.to_html(
                 templates.article, {
                 title : article.title,
                 description : article.description,
@@ -69,7 +69,7 @@ task('default', [], function (params) {
                 head : templates.head,
                 foot : templates.foot,
                 article : article.body
-            });
+            }), '\n');
         
         fs.writeFileSync(outdir + article.out, html, 'utf8');
         console.log('> created ' + outdir + article.out);

From a5027d343aebeeac9431270c346a42af05d03795 Mon Sep 17 00:00:00 2001
From: Philip Peitsch <philip.peitsch@gmail.com>
Date: Tue, 29 Jan 2013 22:43:53 +1100
Subject: [PATCH 2/5] Regenrated all source files with consistent EOL style

---
 about-getting-started.html  |  83 +++++++++++-----------
 about-including-readme.html |  13 ++--
 about-jsdoc3.html           |   1 +
 about-license-jsdoc3.html   |   1 +
 about-namepaths.html        |  57 ++++++++--------
 about-plugins.html          |   1 +
 about-testing-jsdoc3.html   |  71 +++++++++----------
 about-tutorials.html        |   1 +
 howto-commonjs-modules.html |  89 ++++++++++++------------
 index.html                  | 133 ++++++++++++++++++------------------
 plugins-markdown.html       |   1 +
 tags-augments.html          |  79 ++++++++++-----------
 tags-author.html            |  49 ++++++-------
 tags-borrows.html           |  43 ++++++------
 tags-callback.html          |  65 +++++++++---------
 tags-classdesc.html         |  55 +++++++--------
 tags-constant.html          |  65 +++++++++---------
 tags-constructor.html       |  47 ++++++-------
 tags-constructs.html        |  35 +++++-----
 tags-copyright.html         |  41 +++++------
 tags-default.html           |  35 +++++-----
 tags-deprecated.html        |  35 +++++-----
 tags-description.html       |  51 +++++++-------
 tags-enum.html              |  51 +++++++-------
 tags-event.html             |  81 +++++++++++-----------
 tags-example.html           |  31 +++++----
 tags-exports.html           |  45 ++++++------
 tags-file.html              |  49 ++++++-------
 tags-fires.html             |  37 +++++-----
 tags-global.html            |  27 ++++----
 tags-ignore.html            |  31 +++++----
 tags-inner.html             |  31 +++++----
 tags-instance.html          |  31 +++++----
 tags-kind.html              |  31 +++++----
 tags-license.html           |  31 +++++----
 tags-member.html            |  31 +++++----
 tags-memberof.html          |  31 +++++----
 tags-method.html            |  31 +++++----
 tags-mixes.html             |  31 +++++----
 tags-mixin.html             |  31 +++++----
 tags-module.html            |  31 +++++----
 tags-name.html              |  31 +++++----
 tags-namespace.html         |  31 +++++----
 tags-param.html             |  81 +++++++++++-----------
 tags-private.html           |  31 +++++----
 tags-property.html          |  53 +++++++-------
 tags-protected.html         |  31 +++++----
 tags-public.html            |  31 +++++----
 tags-readonly.html          |  31 +++++----
 tags-requires.html          |  31 +++++----
 tags-returns.html           |  39 +++++------
 tags-see.html               |  31 +++++----
 tags-since.html             |  31 +++++----
 tags-summary.html           |  31 +++++----
 tags-this.html              |  31 +++++----
 tags-throws.html            |  31 +++++----
 tags-todo.html              |  31 +++++----
 tags-tutorial.html          |  31 +++++----
 tags-type.html              |  31 +++++----
 tags-typedef.html           |  31 +++++----
 tags-version.html           |  47 ++++++-------
 61 files changed, 1245 insertions(+), 1184 deletions(-)

diff --git a/about-getting-started.html b/about-getting-started.html
index 8679ce57..173a6508 100644
--- a/about-getting-started.html
+++ b/about-getting-started.html
@@ -175,23 +175,23 @@
 	
 	<article>
 	<h1>Getting Started with JSDoc 3</h1>
-
-<h3>Getting Started</h3>
-
-<p>
-JSDoc 3 is an API documentation generator for JavaScript, similar to JavaDoc or PHPDoc. You add documentation comments directly to your source code, right along side the code itself. The JSDoc Tool will scan your source code, and generate a complete HTML documentation website for you.
-</p>
-
-<h3>Adding Documentation Comments to Your Code</h3>
-
-<p>
-JSDoc's purpose is to document the API of your JavaScript application or library. It is assumed that you will want to document things like: namespaces, classes, methods, method parameters, etc.
-</p>
-
-<p>
-JSDoc comments should generally be placed immediately before the code being documented. It must start with a <code>/**</code> sequence in order to be recognized by the JSDoc parser. Comments beginning with <code>/*</code>, <code>/***</code>, or more than 3 stars will be ignored. This is a feature to allow you to suppress parsing of comment blocks.
-</p>
-
+
+<h3>Getting Started</h3>
+
+<p>
+JSDoc 3 is an API documentation generator for JavaScript, similar to JavaDoc or PHPDoc. You add documentation comments directly to your source code, right along side the code itself. The JSDoc Tool will scan your source code, and generate a complete HTML documentation website for you.
+</p>
+
+<h3>Adding Documentation Comments to Your Code</h3>
+
+<p>
+JSDoc's purpose is to document the API of your JavaScript application or library. It is assumed that you will want to document things like: namespaces, classes, methods, method parameters, etc.
+</p>
+
+<p>
+JSDoc comments should generally be placed immediately before the code being documented. It must start with a <code>/**</code> sequence in order to be recognized by the JSDoc parser. Comments beginning with <code>/*</code>, <code>/***</code>, or more than 3 stars will be ignored. This is a feature to allow you to suppress parsing of comment blocks.
+</p>
+
 <dl class="example">
 <dt>The simplest documentation is just a description.</dt>
 <dd>
@@ -202,14 +202,14 @@ <h3>Adding Documentation Comments to Your Code</h3>
 
 </pre>
 </dd>
-</dl><p>
-Adding a description is simple, just type the description you want in the documentaton comment.
-</p>
-
-<p>
-Special "documentation tags" can be used to give more information. For example, if the function is a constructor, you can indicate this by adding a tag.
-</p>
-
+</dl><p>
+Adding a description is simple, just type the description you want in the documentaton comment.
+</p>
+
+<p>
+Special "documentation tags" can be used to give more information. For example, if the function is a constructor, you can indicate this by adding a tag.
+</p>
+
 <dl class="example">
 <dt>Use a documentation tag to describe your code.</dt>
 <dd>
@@ -223,10 +223,10 @@ <h3>Adding Documentation Comments to Your Code</h3>
 
 </pre>
 </dd>
-</dl><p>
-More tags can be used to add more information. See the Tag Dictionary for a complete list of tags that are recognized by JSDoc 3.
-</p>
-
+</dl><p>
+More tags can be used to add more information. See the Tag Dictionary for a complete list of tags that are recognized by JSDoc 3.
+</p>
+
 <dl class="example">
 <dt>Adding more information with tags.</dt>
 <dd>
@@ -242,16 +242,16 @@ <h3>Adding Documentation Comments to Your Code</h3>
 
 </pre>
 </dd>
-</dl><h3>Generating A Website</h3>
-
-<p>
-Once your code is commented, you can use the JSDoc 3 Tool to generate an HTML website from the source.
-</p>
-
-<p>
-By default, JSDoc will use the "default" template to turn the documentation data into HTML. You can edit this template to suit your own needs, or create an entirely new template if that is what you prefer.
-</p>
-
+</dl><h3>Generating A Website</h3>
+
+<p>
+Once your code is commented, you can use the JSDoc 3 Tool to generate an HTML website from the source.
+</p>
+
+<p>
+By default, JSDoc will use the "default" template to turn the documentation data into HTML. You can edit this template to suit your own needs, or create an entirely new template if that is what you prefer.
+</p>
+
 <dl class="example">
 <dt>Running the documentation generator on the command line.</dt>
 <dd>
@@ -260,8 +260,8 @@ <h3>Adding Documentation Comments to Your Code</h3>
 
 </pre>
 </dd>
-</dl><p>
-This command will create a folder named "out" in the current working directory. Within that you will find the generated HTML pages.
+</dl><p>
+This command will create a folder named "out" in the current working directory. Within that you will find the generated HTML pages.
 </p>
     </article>
     
@@ -274,3 +274,4 @@ <h3>Adding Documentation Comments to Your Code</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/about-including-readme.html b/about-including-readme.html
index ade4241a..add4bcf8 100644
--- a/about-including-readme.html
+++ b/about-including-readme.html
@@ -175,11 +175,11 @@
 	
 	<article>
 	<h1>Including a Readme File With JSDoc 3</h1>
-
-<h3>Including a Readme File in Your Documentation With JSDoc 3</h3>
-
-<p>To include a readme file in your documentation, you simply specify the location of your readme file on the command line along with the location of your source files. The readme file will be incorporated into the index.html of your documentation in the default template. The file must be written in markdown and given a .md extension.</p>
-
+
+<h3>Including a Readme File in Your Documentation With JSDoc 3</h3>
+
+<p>To include a readme file in your documentation, you simply specify the location of your readme file on the command line along with the location of your source files. The readme file will be incorporated into the index.html of your documentation in the default template. The file must be written in markdown and given a .md extension.</p>
+
 <dl class="example">
 <dt>Including a readme file in your documentation</dt>
 <dd>
@@ -188,7 +188,7 @@ <h3>Including a Readme File in Your Documentation With JSDoc 3</h3>
 
 </pre>
 </dd>
-</dl><p>If your file is successfully incorporated into the default template, it's content will be rendered in beautiful HTML just before the files list.</p>
+</dl><p>If your file is successfully incorporated into the default template, it's content will be rendered in beautiful HTML just before the files list.</p>
 
     </article>
     
@@ -201,3 +201,4 @@ <h3>Including a Readme File in Your Documentation With JSDoc 3</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/about-jsdoc3.html b/about-jsdoc3.html
index 1041da85..875dc10f 100644
--- a/about-jsdoc3.html
+++ b/about-jsdoc3.html
@@ -365,3 +365,4 @@ <h2>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/about-license-jsdoc3.html b/about-license-jsdoc3.html
index 07fd9cf9..c898ae30 100644
--- a/about-license-jsdoc3.html
+++ b/about-license-jsdoc3.html
@@ -315,3 +315,4 @@ <h2>TaffyDB</h2>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/about-namepaths.html b/about-namepaths.html
index b885d291..7558586b 100644
--- a/about-namepaths.html
+++ b/about-namepaths.html
@@ -175,13 +175,13 @@
 	
 	<article>
 	<h1>Using namepaths with JSDoc 3</h1>
-
-<h3>Namepaths in JSDoc 3</h3>
-
-<p>
-When referring to a JavaScript variable that is elsewhere in your documentation, you must provide a unique identifier that maps to that variable. A namepath provides a way to do so and disambiguate between instance members, static members and inner variables.
-</p>
-
+
+<h3>Namepaths in JSDoc 3</h3>
+
+<p>
+When referring to a JavaScript variable that is elsewhere in your documentation, you must provide a unique identifier that maps to that variable. A namepath provides a way to do so and disambiguate between instance members, static members and inner variables.
+</p>
+
 <dl class="example">
 <dt>Basic Syntax Examples of Nameptahs in JSDoc 3</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Namepaths in JSDoc 3</h3>
 
 </pre>
 </dd>
-</dl><p>
-The example below shows: an <em>instance</em> method named "say," an <em>inner</em> function also named "say," and a <em>static</em> method also named "say." These are three distinct methods that all exist independently of one another.
-</p>
-
+</dl><p>
+The example below shows: an <em>instance</em> method named "say," an <em>inner</em> function also named "say," and a <em>static</em> method also named "say." These are three distinct methods that all exist independently of one another.
+</p>
+
 <dl class="example">
 <dt>Use a documentation tag to describe your code.</dt>
 <dd>
@@ -223,10 +223,10 @@ <h3>Namepaths in JSDoc 3</h3>
 
 </pre>
 </dd>
-</dl><p>
-You would use three different namepath syntaxes to refer to the three different methods:
-</p>
-
+</dl><p>
+You would use three different namepath syntaxes to refer to the three different methods:
+</p>
+
 <dl class="example">
 <dt>Use a documentation tag to describe your code.</dt>
 <dd>
@@ -237,14 +237,14 @@ <h3>Namepaths in JSDoc 3</h3>
 
 </pre>
 </dd>
-</dl><p>
-You might wonder why there is a syntax to refer to an inner method when that method isn't directly accessible from outside the function it is defined in. While that is true, and thus the "~" syntax is rarely used, it <em>is</em> possible to return a reference to an inner method from another method inside that container, so it is possible that some object elsewhere in your code might borrow an inner method.
-</p>
-
-<p>
-Note that if a constructor has an instance member that is also a constructor, you can simply chain the namepaths together to form a longer namepath:
-<p>
-
+</dl><p>
+You might wonder why there is a syntax to refer to an inner method when that method isn't directly accessible from outside the function it is defined in. While that is true, and thus the "~" syntax is rarely used, it <em>is</em> possible to return a reference to an inner method from another method inside that container, so it is possible that some object elsewhere in your code might borrow an inner method.
+</p>
+
+<p>
+Note that if a constructor has an instance member that is also a constructor, you can simply chain the namepaths together to form a longer namepath:
+<p>
+
 <dl class="example">
 <dt>Use a documentation tag to describe your code.</dt>
 <dd>
@@ -265,11 +265,11 @@ <h3>Namepaths in JSDoc 3</h3>
 
 </pre>
 </dd>
-</dl><p>
-In this case, to refer to the method named "consider," you would use the following namepath:
-<code>Person#Idea#consider</code></p>
-
-<p>
+</dl><p>
+In this case, to refer to the method named "consider," you would use the following namepath:
+<code>Person#Idea#consider</code></p>
+
+<p>
 This chaining can be used with any combination of the connecting symbols: <code># . ~</code></p>
 
     </article>
@@ -283,3 +283,4 @@ <h3>Namepaths in JSDoc 3</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/about-plugins.html b/about-plugins.html
index c003137f..d376c752 100644
--- a/about-plugins.html
+++ b/about-plugins.html
@@ -838,3 +838,4 @@ <h2 name="packaging-jsdoc-3-plugins" id="packaging-jsdoc-3-plugins">
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/about-testing-jsdoc3.html b/about-testing-jsdoc3.html
index 7c9fa4c3..52956d5e 100644
--- a/about-testing-jsdoc3.html
+++ b/about-testing-jsdoc3.html
@@ -175,15 +175,15 @@
 	
 	<article>
 	<h1>Testing JSDoc 3</h1>
-
-
-<h1>Testing JSDoc 3</h1>
-
-<h2>Running Tests</h2>
-
-<p>Running tests is easy.  Just change your working directory to the jsdoc folder
-and run the following command on Windows:</p>
-
+
+
+<h1>Testing JSDoc 3</h1>
+
+<h2>Running Tests</h2>
+
+<p>Running tests is easy.  Just change your working directory to the jsdoc folder
+and run the following command on Windows:</p>
+
 <dl class="example">
 <dt>Example</dt>
 <dd>
@@ -192,8 +192,8 @@ <h2>Running Tests</h2>
 
 </pre>
 </dd>
-</dl><p>... or on a Max OSX or *nix platform:</p>
-
+</dl><p>... or on a Max OSX or *nix platform:</p>
+
 <dl class="example">
 <dt>Example</dt>
 <dd>
@@ -202,8 +202,8 @@ <h2>Running Tests</h2>
 
 </pre>
 </dd>
-</dl><p>If you can't get the short-form commands to work, try invoking Java directly:</p>
-
+</dl><p>If you can't get the short-form commands to work, try invoking Java directly:</p>
+
 <dl class="example">
 <dt>Example</dt>
 <dd>
@@ -214,28 +214,28 @@ <h2>Running Tests</h2>
 
 </pre>
 </dd>
-</dl><h2>Writing Tests</h2>
-
-<p>Adding tests is pretty easy, too.  You can write tests for JSDoc itself (to 
-make sure tags and the parser, etc. are working properly), tests for plugins, and/or
-tests for templates.</p>
-
-<p>JSDoc 3 uses Jasmine (https://github.com/pivotal/jasmine) as its testing framework.
-Take a look at that project's wiki for documentation on writing tests in general.</p>
-
-<h3>Tests for JSDoc</h3>
-
-<p>Take a look at the files in the <code>test</code> directory for many examples of
-writing tests for JSDoc itself.  the <code>test\fixtures</code> directory hold fixtures
-for use in the tests and the <code>test\specs</code> directory holds the tests themselves.</p>
-
-<h3>Tests for plugins</h3>
-
-<p>Tests for plugins are found in <code>plugins\test</code> directory.   Plugins containing
-tests that were installed with the Jakefile install task will be run automatically.</p>
-
-<h3>Tests for templates</h3>
-
+</dl><h2>Writing Tests</h2>
+
+<p>Adding tests is pretty easy, too.  You can write tests for JSDoc itself (to 
+make sure tags and the parser, etc. are working properly), tests for plugins, and/or
+tests for templates.</p>
+
+<p>JSDoc 3 uses Jasmine (https://github.com/pivotal/jasmine) as its testing framework.
+Take a look at that project's wiki for documentation on writing tests in general.</p>
+
+<h3>Tests for JSDoc</h3>
+
+<p>Take a look at the files in the <code>test</code> directory for many examples of
+writing tests for JSDoc itself.  the <code>test\fixtures</code> directory hold fixtures
+for use in the tests and the <code>test\specs</code> directory holds the tests themselves.</p>
+
+<h3>Tests for plugins</h3>
+
+<p>Tests for plugins are found in <code>plugins\test</code> directory.   Plugins containing
+tests that were installed with the Jakefile install task will be run automatically.</p>
+
+<h3>Tests for templates</h3>
+
 <p>TODO</p>
     </article>
     
@@ -248,3 +248,4 @@ <h3>Tests for templates</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/about-tutorials.html b/about-tutorials.html
index 20c2e089..377288ee 100644
--- a/about-tutorials.html
+++ b/about-tutorials.html
@@ -304,3 +304,4 @@ <h5>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/howto-commonjs-modules.html b/howto-commonjs-modules.html
index 5f133960..9bd153e2 100644
--- a/howto-commonjs-modules.html
+++ b/howto-commonjs-modules.html
@@ -175,19 +175,19 @@
 	
 	<article>
 	<h1>Document CommonJS Modules</h1>
-
-<h3>Overview</h3>
-
-<p>
-JSDoc 3 has built-in support for JavaScript code that is written to conform to the <a href="http://wiki.commonjs.org/wiki/Modules/1.1">CommonJS Modules standard</a>. This allows you to easily document your own JavaScript modules and the members they export.
-</p>
-
-<h3>Document a Simple CommonJS Module</h3>
-
-<p>
-Add a single <code>@module &lt;module identifier></code> tag at the top of the file that defines your module and any documented members of the <code>exports</code> object in that file will automatically be included in the documentation for that module.
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+JSDoc 3 has built-in support for JavaScript code that is written to conform to the <a href="http://wiki.commonjs.org/wiki/Modules/1.1">CommonJS Modules standard</a>. This allows you to easily document your own JavaScript modules and the members they export.
+</p>
+
+<h3>Document a Simple CommonJS Module</h3>
+
+<p>
+Add a single <code>@module &lt;module identifier></code> tag at the top of the file that defines your module and any documented members of the <code>exports</code> object in that file will automatically be included in the documentation for that module.
+</p>
+
 <dl class="example">
 <dt>The putOn and unbutton methods are documented as members of the &quot;my/shirt&quot; module.</dt>
 <dd>
@@ -204,12 +204,12 @@ <h3>Document a Simple CommonJS Module</h3>
 
 </pre>
 </dd>
-</dl><h3>Document Members Assigned to <code>module.exports</code></h3>
-
-<p>
-Some implementations of the CommonJS Modules standard allow you to assign an object literal to the <code>module.exports</code> namespace directly. This pattern is automatically supported by JSDoc 3.
-</p>
-
+</dl><h3>Document Members Assigned to <code>module.exports</code></h3>
+
+<p>
+Some implementations of the CommonJS Modules standard allow you to assign an object literal to the <code>module.exports</code> namespace directly. This pattern is automatically supported by JSDoc 3.
+</p>
+
 <dl class="example">
 <dt>The blend and darken methods are documented as members of the &quot;color/mixer&quot; module.</dt>
 <dd>
@@ -226,12 +226,12 @@ <h3>Document a Simple CommonJS Module</h3>
 
 </pre>
 </dd>
-</dl><h3>Document Members Exported on the Global <code>this</code></h3>
-
-<p>
-JSDoc 3 understands the NodeJS convention of exporting properties and functions when they are assigned to a global <code>this</code> variable, as shown below.
-</p>
-
+</dl><h3>Document Members Exported on the Global <code>this</code></h3>
+
+<p>
+JSDoc 3 understands the NodeJS convention of exporting properties and functions when they are assigned to a global <code>this</code> variable, as shown below.
+</p>
+
 <dl class="example">
 <dt>The Book class is documented as a member of the &quot;bookshelf&quot; module.</dt>
 <dd>
@@ -250,10 +250,10 @@ <h3>Document a Simple CommonJS Module</h3>
 
 </pre>
 </dd>
-</dl><h3>Document a Function that returns a RequireJS Module</h3>
-
-<p>The RequireJS library provides a <code>define</code> method that allows you to write a function to return a module object. Use the <code>@exports</code> tag to document that all the members of an object literal should be documented as members of a module.</p>
-
+</dl><h3>Document a Function that returns a RequireJS Module</h3>
+
+<p>The RequireJS library provides a <code>define</code> method that allows you to write a function to return a module object. Use the <code>@exports</code> tag to document that all the members of an object literal should be documented as members of a module.</p>
+
 <dl class="example">
 <dt>The color property and the Turtleneck class are documented as members of the &quot;my/shirt&quot; module.</dt>
 <dd>
@@ -281,10 +281,10 @@ <h3>Document a Simple CommonJS Module</h3>
 
 </pre>
 </dd>
-</dl><h3>Document a Module as a Constructor</h3>
-
-<p>The following examples illustrate patterns for documenting modules that are constructors.</p>
-
+</dl><h3>Document a Module as a Constructor</h3>
+
+<p>The following examples illustrate patterns for documenting modules that are constructors.</p>
+
 <dl class="example">
 <dt>Use the @alias tag simplify documenting a constructor-module in RequireJS.</dt>
 <dd>
@@ -310,8 +310,8 @@ <h3>Document a Simple CommonJS Module</h3>
 
 </pre>
 </dd>
-</dl><p>The same pattern can be documented in CommonJS environments.</p>
-
+</dl><p>The same pattern can be documented in CommonJS environments.</p>
+
 <dl class="example">
 <dt>Use the @alias tag to document constructor-modules in CommonJS.</dt>
 <dd>
@@ -336,10 +336,10 @@ <h3>Document a Simple CommonJS Module</h3>
 
 </pre>
 </dd>
-</dl><h3>Document Multiple RequireJS Modules Defined in a Single File</h3>
-
-<p>If you have multiple calls to <code>define</code> in a single file use the <code>@exports</code> tag to document each function that returns module code. Name the exported objects "exports" and JSDoc 3 will automatically document any of their members as members of their module.</p>
-
+</dl><h3>Document Multiple RequireJS Modules Defined in a Single File</h3>
+
+<p>If you have multiple calls to <code>define</code> in a single file use the <code>@exports</code> tag to document each function that returns module code. Name the exported objects "exports" and JSDoc 3 will automatically document any of their members as members of their module.</p>
+
 <dl class="example">
 <dt>The getStyleProperty and isInHead methods are documented as members of the &quot;html/utils&quot; module. The Tag class is documented as a member of the &quot;tag&quot; module.</dt>
 <dd>
@@ -378,11 +378,11 @@ <h3>Document a Simple CommonJS Module</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="http://requirejs.org/docs/api.html#define">Defining RequireJS Modules</a></li>
-    <li><a href="http://nodejs.org/docs/v0.4.1/api/modules.html">NodeJS Modules Tutorial</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="http://requirejs.org/docs/api.html#define">Defining RequireJS Modules</a></li>
+    <li><a href="http://nodejs.org/docs/v0.4.1/api/modules.html">NodeJS Modules Tutorial</a></li>
 </ul>
     </article>
     
@@ -395,3 +395,4 @@ <h3>Document a Simple CommonJS Module</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/index.html b/index.html
index dbae8157..05db006f 100644
--- a/index.html
+++ b/index.html
@@ -175,66 +175,66 @@
 	
 	<article>
 	<h1>Index</h1>
-
-
-<h2>Table of Contents</h2>
-
-<ol>
-	<li>
-		<a href="#Getting_Started">Getting Started</a>
-	</li>
-
-	<li>
-		<a href="#JSDoc_Examples">JSDoc Examples</a>
-	</li>
-
-	<li>
-		<a href="#Contribute">Contribute</a>
-	</li>
-
-	<li>
-		<a href="#JSDoc3_Tag_Dictionary">JSDoc 3 Tag Dictionary</a>
-	</li>
-</ol>
-
-<h2 name="Getting_Started" id="Getting_Started">Getting Started</h2>
-<dl>
-	<dt><a href="about-jsdoc3.html">README</a></dt>
-        <dd>Basic info on JSDoc 3.</dd>
-	<dt><a href="about-getting-started.html">An introduction to JSDoc 3</a></dt>
-		<dd>A quick-start to documenting JavaScript with JSDoc.</dd>
-	<dt><a href="about-namepaths.html">Using namepaths with JSDoc 3.</a></dt>
-		<dd>A guide to using namepaths with JSDoc 3.</dd>
-    <dt><a href="about-tutorials.html">Tutorials mechanism</a></dt>
-        <dd>Additional longtext tutorials for your code.</dd>
-	<dt><a href="about-including-readme.html">Adding Content to Index.html</a></dt>
-        <dd>Using Readme files to add content to the default index.html</dd>
-	<dt><a href="about-plugins.html">All about plugins</a></dt>
-        <dd>Installing plugins and writing your own.</dd>
-	<dt><a href="plugins-markdown.html">Configuring the markdown plugin</a></dt>
-        <dd>This allows markdown in code comments and offers 2 flavors.</dd>
-	<dt><a href="about-testing-jsdoc3.html">Testing JSDoc 3</a></dt>
-        <dd>About running the self tests included with JSDoc 3.</dd>
-	<dt><a href="about-license-jsdoc3.html">License</a></dt>
-        <dd>The license covering JSDoc 3 code.</dd>
-</dl>
-
-<h2 name="JSDoc_Examples" id="JSDoc_Examples">JSDoc Examples</h2>
-<dl>
-	<dt><a href="howto-commonjs-modules.html">CommonJS Modules</a></dt>
-		<dd>Documenting code that conforms to the CommonJS server-side modules standard.</dd>
-</dl>
-
-<h2 name="Contribute" id="Contribute">Contribute</h2>
-<dl>
-	<dt><a href="https://github.com/jsdoc3/jsdoc">JSDoc 3 at github</a></dt>
-		<dd>Contribute to the JSDoc 3 project.</dd>
-	<dt><a href="https://github.com/jsdoc3/jsdoc3.github.com">JSDoc 3 Documentation</a></dt>
-		<dd>Contribute to the JSDoc 3 Documentation project.</dd>
-</dl>
-
-<h2 name="JSDoc3_Tag_Dictionary" id="JSDoc3_Tag_Dictionary">JSDoc 3 Tag Dictionary</h2>
-<dl>
+
+
+<h2>Table of Contents</h2>
+
+<ol>
+	<li>
+		<a href="#Getting_Started">Getting Started</a>
+	</li>
+
+	<li>
+		<a href="#JSDoc_Examples">JSDoc Examples</a>
+	</li>
+
+	<li>
+		<a href="#Contribute">Contribute</a>
+	</li>
+
+	<li>
+		<a href="#JSDoc3_Tag_Dictionary">JSDoc 3 Tag Dictionary</a>
+	</li>
+</ol>
+
+<h2 name="Getting_Started" id="Getting_Started">Getting Started</h2>
+<dl>
+	<dt><a href="about-jsdoc3.html">README</a></dt>
+        <dd>Basic info on JSDoc 3.</dd>
+	<dt><a href="about-getting-started.html">An introduction to JSDoc 3</a></dt>
+		<dd>A quick-start to documenting JavaScript with JSDoc.</dd>
+	<dt><a href="about-namepaths.html">Using namepaths with JSDoc 3.</a></dt>
+		<dd>A guide to using namepaths with JSDoc 3.</dd>
+    <dt><a href="about-tutorials.html">Tutorials mechanism</a></dt>
+        <dd>Additional longtext tutorials for your code.</dd>
+	<dt><a href="about-including-readme.html">Adding Content to Index.html</a></dt>
+        <dd>Using Readme files to add content to the default index.html</dd>
+	<dt><a href="about-plugins.html">All about plugins</a></dt>
+        <dd>Installing plugins and writing your own.</dd>
+	<dt><a href="plugins-markdown.html">Configuring the markdown plugin</a></dt>
+        <dd>This allows markdown in code comments and offers 2 flavors.</dd>
+	<dt><a href="about-testing-jsdoc3.html">Testing JSDoc 3</a></dt>
+        <dd>About running the self tests included with JSDoc 3.</dd>
+	<dt><a href="about-license-jsdoc3.html">License</a></dt>
+        <dd>The license covering JSDoc 3 code.</dd>
+</dl>
+
+<h2 name="JSDoc_Examples" id="JSDoc_Examples">JSDoc Examples</h2>
+<dl>
+	<dt><a href="howto-commonjs-modules.html">CommonJS Modules</a></dt>
+		<dd>Documenting code that conforms to the CommonJS server-side modules standard.</dd>
+</dl>
+
+<h2 name="Contribute" id="Contribute">Contribute</h2>
+<dl>
+	<dt><a href="https://github.com/jsdoc3/jsdoc">JSDoc 3 at github</a></dt>
+		<dd>Contribute to the JSDoc 3 project.</dd>
+	<dt><a href="https://github.com/jsdoc3/jsdoc3.github.com">JSDoc 3 Documentation</a></dt>
+		<dd>Contribute to the JSDoc 3 Documentation project.</dd>
+</dl>
+
+<h2 name="JSDoc3_Tag_Dictionary" id="JSDoc3_Tag_Dictionary">JSDoc 3 Tag Dictionary</h2>
+<dl>
 	<dt><a href="tags-augments.html">@augments</a></dt>
 		<dd>This object adds onto a parent object.</dd>	<dt><a href="tags-author.html">@author</a></dt>
 		<dd>Documents the author of an item.</dd>	<dt><a href="tags-borrows.html">@borrows</a></dt>
@@ -285,12 +285,12 @@ <h2 name="JSDoc3_Tag_Dictionary" id="JSDoc3_Tag_Dictionary">JSDoc 3 Tag Dictiona
 		<dd>Insert a link to an included tutorial file.</dd>	<dt><a href="tags-type.html">@type</a></dt>
 		<dd>[todo] Document the type of an object.</dd>	<dt><a href="tags-typedef.html">@typedef</a></dt>
 		<dd>[todo] Document a custom type.</dd>	<dt><a href="tags-version.html">@version</a></dt>
-		<dd>Documents the version number of an item.</dd></dl>
-
-<p>
-<link href="styles/css3-github-ribbon.css" rel="stylesheet" />
-<a href="https://github.com/jsdoc3/jsdoc" class="github-ribbon">Fork me on GitHub</a>
-</p>
+		<dd>Documents the version number of an item.</dd></dl>
+
+<p>
+<link href="styles/css3-github-ribbon.css" rel="stylesheet" />
+<a href="https://github.com/jsdoc3/jsdoc" class="github-ribbon">Fork me on GitHub</a>
+</p>
 
     </article>
     
@@ -303,3 +303,4 @@ <h2 name="JSDoc3_Tag_Dictionary" id="JSDoc3_Tag_Dictionary">JSDoc 3 Tag Dictiona
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/plugins-markdown.html b/plugins-markdown.html
index 79162b18..2cdffe5d 100644
--- a/plugins-markdown.html
+++ b/plugins-markdown.html
@@ -310,3 +310,4 @@ <h2>Extended tag support</h2>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-augments.html b/tags-augments.html
index 66e97c0f..58173e6a 100644
--- a/tags-augments.html
+++ b/tags-augments.html
@@ -175,34 +175,34 @@
 	
 	<article>
 	<h1>@augments</h1>
-
-
-<h3>Synonyms</h3>
-
-<ul>
-    <li>@extends</li>
-</ul>
-
-<h3>Syntax</h3>
-
-<code>@augments &lt;namepath&gt;</code>
-
-<h3>Overview</h3>
-
-<p>
-    The @augments or @extends tag marks a symbol as augmenting another symbol.
-</p>
-
-<p>
-    While current versions of JavaScript don't allow classes or subclasses in the same way that class-based languages like Java do, many programmers choose to think of their code structure in these terms. For this purpose JSDoc provides the @class and @extends tags. If you wish to express a similar relationship between two symbols, but don't wish to promote the classical analogy, you can use the @contructor and @augments tags instead.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-    In the example below I wish to document the fact that Ducks are a specialised form of Animal: meaning that Duck instances are like Animal instances which have been augmented with additional properties.
-</p>
-
+
+
+<h3>Synonyms</h3>
+
+<ul>
+    <li>@extends</li>
+</ul>
+
+<h3>Syntax</h3>
+
+<code>@augments &lt;namepath&gt;</code>
+
+<h3>Overview</h3>
+
+<p>
+    The @augments or @extends tag marks a symbol as augmenting another symbol.
+</p>
+
+<p>
+    While current versions of JavaScript don't allow classes or subclasses in the same way that class-based languages like Java do, many programmers choose to think of their code structure in these terms. For this purpose JSDoc provides the @class and @extends tags. If you wish to express a similar relationship between two symbols, but don't wish to promote the classical analogy, you can use the @contructor and @augments tags instead.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+    In the example below I wish to document the fact that Ducks are a specialised form of Animal: meaning that Duck instances are like Animal instances which have been augmented with additional properties.
+</p>
+
 <dl class="example">
 <dt>Documenting a class/subclass type of relationship.</dt>
 <dd>
@@ -237,17 +237,17 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><p>
-    A related pattern can be documented with the @mixin and @mixes tags. Or, if the augmented symbol is only reusing one or two members of another symbol, you may find the @borrows tag more convenient.
-</p>
-
-<h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-constructor.html">@constructor or @class</a></li>
-    <li><a href="tags-mixin.html">@mixin</a></li>
-    <li><a href="tags-mixes.html">@mixes</a></li>
-    <li><a href="tags-borrows.html">@borrows</a></li>
+</dl><p>
+    A related pattern can be documented with the @mixin and @mixes tags. Or, if the augmented symbol is only reusing one or two members of another symbol, you may find the @borrows tag more convenient.
+</p>
+
+<h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-constructor.html">@constructor or @class</a></li>
+    <li><a href="tags-mixin.html">@mixin</a></li>
+    <li><a href="tags-mixes.html">@mixes</a></li>
+    <li><a href="tags-borrows.html">@borrows</a></li>
 </ul>
     </article>
     
@@ -260,3 +260,4 @@ <h3>See Also</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-author.html b/tags-author.html
index 97eefe04..3804ccc3 100644
--- a/tags-author.html
+++ b/tags-author.html
@@ -175,19 +175,19 @@
 	
 	<article>
 	<h1>@author</h1>
-
-
-<h3>Overview</h3>
-
-<p>Document the author of an item. The text following the @author tag 
-will be used to describe the author in the default template.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+
+<h3>Overview</h3>
+
+<p>Document the author of an item. The text following the @author tag 
+will be used to describe the author in the default template.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Documenting the author of an item.</dt>
 <dd>
@@ -202,17 +202,17 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-version.html">@version</a></li>
-	<li><a href="tags-file.html">@file</a></li>
-</ul>
-
-<h5>Contributers to these docs</h5>
-
-<ul>
-    <li><a href="https://github.com/matthewkastor">matthewkastor</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-version.html">@version</a></li>
+	<li><a href="tags-file.html">@file</a></li>
+</ul>
+
+<h5>Contributers to these docs</h5>
+
+<ul>
+    <li><a href="https://github.com/matthewkastor">matthewkastor</a></li>
 </ul>
     </article>
     
@@ -225,3 +225,4 @@ <h5>Contributers to these docs</h5>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-borrows.html b/tags-borrows.html
index 2900d47b..0b25c612 100644
--- a/tags-borrows.html
+++ b/tags-borrows.html
@@ -175,27 +175,27 @@
 	
 	<article>
 	<h1>@borrows</h1>
-
-<h3>Syntax</h3>
-
-<code>@borrows &lt;that namepath&gt; as &lt;this namepath&gt;</code>
-
-<h3>Overview</h3>
-
-<p>
-    The @borrows tag allows you to add documentation for another symbol to your documentation.
-</p>
-
-<p>
-    This tag would be useful if you had more than one way to reference a function, but you didn't want to duplicate the same documentation in two places.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-    In this example there exists documentation for the "trstr" function, but "util.trim" is just a reference to that same function by a different name.
-</p>
-
+
+<h3>Syntax</h3>
+
+<code>@borrows &lt;that namepath&gt; as &lt;this namepath&gt;</code>
+
+<h3>Overview</h3>
+
+<p>
+    The @borrows tag allows you to add documentation for another symbol to your documentation.
+</p>
+
+<p>
+    This tag would be useful if you had more than one way to reference a function, but you didn't want to duplicate the same documentation in two places.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+    In this example there exists documentation for the "trstr" function, but "util.trim" is just a reference to that same function by a different name.
+</p>
+
 <dl class="example">
 <dt>Duplicate the documentation for trstr as util.trim</dt>
 <dd>
@@ -229,3 +229,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-callback.html b/tags-callback.html
index 43718a3f..89eb8490 100644
--- a/tags-callback.html
+++ b/tags-callback.html
@@ -175,33 +175,33 @@
 	
 	<article>
 	<h1>@callback</h1>
-
-<h3>Synonyms</h3>
-
-<ul>
-    <li>@typedef {function} &lt;namepath&gt;</li>
-</ul>
-
-<h3>Syntax</h3>
-
-<code>@callback &lt;namepath&gt;</code>
-
-<h3>Overview</h3>
-
-<p>
-    The @callback tag provides information about a callback function that can be passed to other functions, including the callback's parameters and return value. You can include any of the tags that you can provide for a @method.
-</p>
-
-<p>
-    Once you define a callback, you can use it in the same way as a custom type defined with the @typedef tag. In particular, you can use the callback's name as a type name. This allows you to indicate that a function parameter should contain a certain type of callback.
-</p>
-
-<p>
-    If you want a callback to be displayed with the type definitions for a specific class, you can give the callback a namepath indicating that it is an inner function of that class. You can also define a global callback type that is referenced from multiple classes.
-</p>
-
-<h3>Examples</h3>
-
+
+<h3>Synonyms</h3>
+
+<ul>
+    <li>@typedef {function} &lt;namepath&gt;</li>
+</ul>
+
+<h3>Syntax</h3>
+
+<code>@callback &lt;namepath&gt;</code>
+
+<h3>Overview</h3>
+
+<p>
+    The @callback tag provides information about a callback function that can be passed to other functions, including the callback's parameters and return value. You can include any of the tags that you can provide for a @method.
+</p>
+
+<p>
+    Once you define a callback, you can use it in the same way as a custom type defined with the @typedef tag. In particular, you can use the callback's name as a type name. This allows you to indicate that a function parameter should contain a certain type of callback.
+</p>
+
+<p>
+    If you want a callback to be displayed with the type definitions for a specific class, you can give the callback a namepath indicating that it is an inner function of that class. You can also define a global callback type that is referenced from multiple classes.
+</p>
+
+<h3>Examples</h3>
+
 <dl class="example">
 <dt>Documenting a class-specific callback</dt>
 <dd>
@@ -254,11 +254,11 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-method.html">@method or @function</a></li>
-    <li><a href="tags-typedef.html">@typedef</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-method.html">@method or @function</a></li>
+    <li><a href="tags-typedef.html">@typedef</a></li>
 </ul>
     </article>
     
@@ -271,3 +271,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-classdesc.html b/tags-classdesc.html
index 0a1361f2..fd7c9f97 100644
--- a/tags-classdesc.html
+++ b/tags-classdesc.html
@@ -175,28 +175,28 @@
 	
 	<article>
 	<h1>@classdesc</h1>
-
-<h3>Syntax</h3>
-
-<code>@class &lt;SomeClassName&gt;<br>
-@classdesc &lt;some description&gt;</code>
-
-<h3>Overview</h3>
-
-<p>
-    The @classdesc tag is used to provide a description for a class, separate from the constructor function's description.
-</p>
-
-<p>
-    The functionality of the @classdesc tag in JSDoc 3 duplicates that of the @class in previous versions. As of version 3, the syntax and functionality of the @class tag now exactly matches the @constructor tag, and the @classdesc tag more explicitly communicates its purpose: to document a class's description.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-    As shown below, a class has places for two descriptions, one applies to the function itself, while the other applies to the class in general.
-</p>
-
+
+<h3>Syntax</h3>
+
+<code>@class &lt;SomeClassName&gt;<br>
+@classdesc &lt;some description&gt;</code>
+
+<h3>Overview</h3>
+
+<p>
+    The @classdesc tag is used to provide a description for a class, separate from the constructor function's description.
+</p>
+
+<p>
+    The functionality of the @classdesc tag in JSDoc 3 duplicates that of the @class in previous versions. As of version 3, the syntax and functionality of the @class tag now exactly matches the @constructor tag, and the @classdesc tag more explicitly communicates its purpose: to document a class's description.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+    As shown below, a class has places for two descriptions, one applies to the function itself, while the other applies to the class in general.
+</p>
+
 <dl class="example">
 <dt>A doclet with both a description and a class description</dt>
 <dd>
@@ -211,11 +211,11 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-description.html">@description</a></li>
-    <li><a href="tags-constructor.html">@class</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-description.html">@description</a></li>
+    <li><a href="tags-constructor.html">@class</a></li>
 </ul>
     </article>
     
@@ -228,3 +228,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-constant.html b/tags-constant.html
index 4ee90b0b..0e65fa8c 100644
--- a/tags-constant.html
+++ b/tags-constant.html
@@ -175,29 +175,29 @@
 	
 	<article>
 	<h1>@constant</h1>
-
-<h3>Synonyms</h3>
-
-<ul>
-    <li>@const</li>
-</ul>
-
-<h3>Syntax</h3>
-
-<code>@constant [&lt;type> &lt;name>]</code>
-
-<h3>Overview</h3>
-
-<p>
-    The @constant tag is used to mark the documentation as belonging to a symbol that is a constant.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-    In this example we are documenting a string constant. Note that although the code is using the <code>const</code> keyword, this is not required by JSDoc. If your JavaScript host environment doesn't yet support constant declarations, the @const documentation can just as effectively be used on <code>var</code> declarations.
-</p>
-
+
+<h3>Synonyms</h3>
+
+<ul>
+    <li>@const</li>
+</ul>
+
+<h3>Syntax</h3>
+
+<code>@constant [&lt;type> &lt;name>]</code>
+
+<h3>Overview</h3>
+
+<p>
+    The @constant tag is used to mark the documentation as belonging to a symbol that is a constant.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+    In this example we are documenting a string constant. Note that although the code is using the <code>const</code> keyword, this is not required by JSDoc. If your JavaScript host environment doesn't yet support constant declarations, the @const documentation can just as effectively be used on <code>var</code> declarations.
+</p>
+
 <dl class="example">
 <dt>A string constant representing the color red</dt>
 <dd>
@@ -210,15 +210,15 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><p>
-    Note that the example provides the type in a @type tag. This is optional. Also the optional @default tag is used here too, this will automatically add whatever the assigned value is (for example 'FF0000') to the documentation.
-</p>
-
-<h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-default.html">@default</a></li>
-    <li><a href="tags-type.html">@type</a></li>
+</dl><p>
+    Note that the example provides the type in a @type tag. This is optional. Also the optional @default tag is used here too, this will automatically add whatever the assigned value is (for example 'FF0000') to the documentation.
+</p>
+
+<h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-default.html">@default</a></li>
+    <li><a href="tags-type.html">@type</a></li>
 </ul>
     </article>
     
@@ -231,3 +231,4 @@ <h3>See Also</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-constructor.html b/tags-constructor.html
index 30d1ef8f..95eba1de 100644
--- a/tags-constructor.html
+++ b/tags-constructor.html
@@ -175,25 +175,25 @@
 	
 	<article>
 	<h1>@constructor</h1>
-
-<h3>Synonyms</h3>
-
-<ul>
-    <li>@class</li>
-</ul>
-
-<h3>Syntax</h3>
-
-<code>@constructor [&lt;type> &lt;name>]</code>
-
-<h3>Overview</h3>
-
-<p>
-    The @constructor tag marks an function as being a constructor, meant to be called with the new keyword to return an instance.
-</p>
-
-<h3>Examples</h3>
-
+
+<h3>Synonyms</h3>
+
+<ul>
+    <li>@class</li>
+</ul>
+
+<h3>Syntax</h3>
+
+<code>@constructor [&lt;type> &lt;name>]</code>
+
+<h3>Overview</h3>
+
+<p>
+    The @constructor tag marks an function as being a constructor, meant to be called with the new keyword to return an instance.
+</p>
+
+<h3>Examples</h3>
+
 <dl class="example">
 <dt>A function that constructs Person instances.</dt>
 <dd>
@@ -209,10 +209,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-constructs.html">@constructs</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-constructs.html">@constructs</a></li>
 </ul>
     </article>
     
@@ -225,3 +225,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-constructs.html b/tags-constructs.html
index 4a8f1310..ac74013d 100644
--- a/tags-constructs.html
+++ b/tags-constructs.html
@@ -175,19 +175,19 @@
 	
 	<article>
 	<h1>@constructs</h1>
-
-<h3>Overview</h3>
-
-<p>
-When using an object literal to define a class (for example with the <code>@lends</code> tag) the <code>@constructs</code> tag allows you to document that a particular function will be used to construct instances of that class.
-</p>
-
-<h3>Syntax</h3>
-
-<code>@constructs [&lt;name>]</code>
-
-<h3>Examples</h3>
-
+
+<h3>Overview</h3>
+
+<p>
+When using an object literal to define a class (for example with the <code>@lends</code> tag) the <code>@constructs</code> tag allows you to document that a particular function will be used to construct instances of that class.
+</p>
+
+<h3>Syntax</h3>
+
+<code>@constructs [&lt;name>]</code>
+
+<h3>Examples</h3>
+
 <dl class="example">
 <dt>Using the @constructs tag with @lends</dt>
 <dd>
@@ -227,10 +227,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="tag-lends.html">@lends</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tag-lends.html">@lends</a></li>
 </ul>
     </article>
     
@@ -243,3 +243,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-copyright.html b/tags-copyright.html
index 49122892..c71c1f1f 100644
--- a/tags-copyright.html
+++ b/tags-copyright.html
@@ -175,22 +175,22 @@
 	
 	<article>
 	<h1>@copyright</h1>
-
-<h3>Syntax</h3>
-
-<code>@overview<br>@copyright &lt;some copyright text></code>
-
-<h3>Overview</h3>
-
-<p>
-The @copyright tag is used to document copyright information in a file overview comment.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Syntax</h3>
+
+<code>@overview<br>@copyright &lt;some copyright text></code>
+
+<h3>Overview</h3>
+
+<p>
+The @copyright tag is used to document copyright information in a file overview comment.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -202,10 +202,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-file.html">@overview</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-file.html">@overview</a></li>
 </ul>
     </article>
     
@@ -218,3 +218,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-default.html b/tags-default.html
index 1fdd45de..5d1345b1 100644
--- a/tags-default.html
+++ b/tags-default.html
@@ -175,23 +175,23 @@
 	
 	<article>
 	<h1>@default</h1>
-
-<h3>Syntax</h3>
-
-<code>@default [&lt;some value>]</code>
-
-<h3>Overview</h3>
-
-<p>
-The @default tag allows you to document the assigned value of a symbol. You can supply this tag with a value yourself or you can allow JSDoc to automatically document the value from the source code -- only possible when the documented symbol is being assigned a single, simple value that is either: a string, a number, a boolean or null.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-In this example a constant is documented. The value of the constant is <code>0xff0000</code>. By adding the @default tag this value is automatically added to the documentation.
-</p>
-
+
+<h3>Syntax</h3>
+
+<code>@default [&lt;some value>]</code>
+
+<h3>Overview</h3>
+
+<p>
+The @default tag allows you to document the assigned value of a symbol. You can supply this tag with a value yourself or you can allow JSDoc to automatically document the value from the source code -- only possible when the documented symbol is being assigned a single, simple value that is either: a string, a number, a boolean or null.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+In this example a constant is documented. The value of the constant is <code>0xff0000</code>. By adding the @default tag this value is automatically added to the documentation.
+</p>
+
 <dl class="example">
 <dt>Document the number value of a constant</dt>
 <dd>
@@ -216,3 +216,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-deprecated.html b/tags-deprecated.html
index 4b4d7fa8..adb68787 100644
--- a/tags-deprecated.html
+++ b/tags-deprecated.html
@@ -175,23 +175,23 @@
 	
 	<article>
 	<h1>@deprecated</h1>
-
-<h3>Syntax</h3>
-
-<code>@deprecated [&lt;some text>]</code>
-
-<h3>Overview</h3>
-
-<p>
-The @deprecated tag marks a symbol in your code as being deprecated.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-You can use the @deprecated tag by itself, or include some text that describes more about the deprecation.
-</p>
-
+
+<h3>Syntax</h3>
+
+<code>@deprecated [&lt;some text>]</code>
+
+<h3>Overview</h3>
+
+<p>
+The @deprecated tag marks a symbol in your code as being deprecated.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+You can use the @deprecated tag by itself, or include some text that describes more about the deprecation.
+</p>
+
 <dl class="example">
 <dt>Document that the old function has been deprecated since version 2.0</dt>
 <dd>
@@ -216,3 +216,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-description.html b/tags-description.html
index 26988518..251d18af 100644
--- a/tags-description.html
+++ b/tags-description.html
@@ -175,23 +175,23 @@
 	
 	<article>
 	<h1>@desc</h1>
-
-<h3>Syntax</h3>
-
-<code>@desc &lt;some description></code>
-
-<h3>Overview</h3>
-
-<p>
-The @desc tag allows you to provide a general description of the symbol you are documenting. The text can be in the form of HTML or, if you have enabled the markdown plugin, it can be formatted as one of the various flavors or MarkDown.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-The @desc (or it's synonym @description) is the default tag in JSDoc, so if no other tag is in effect you can just start writing your description text.
-</p>
-
+
+<h3>Syntax</h3>
+
+<code>@desc &lt;some description></code>
+
+<h3>Overview</h3>
+
+<p>
+The @desc tag allows you to provide a general description of the symbol you are documenting. The text can be in the form of HTML or, if you have enabled the markdown plugin, it can be formatted as one of the various flavors or MarkDown.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+The @desc (or it's synonym @description) is the default tag in JSDoc, so if no other tag is in effect you can just start writing your description text.
+</p>
+
 <dl class="example">
 <dt>A tagless description is allowed if no other tag is in effect</dt>
 <dd>
@@ -208,10 +208,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><p>
-If any other tag has previously been used in a given doc comment, then you must use a @desc tag if you wish to provide a description.
-</p>
-
+</dl><p>
+If any other tag has previously been used in a given doc comment, then you must use a @desc tag if you wish to provide a description.
+</p>
+
 <dl class="example">
 <dt>A @desc tag is necessary if any other tag is in effect</dt>
 <dd>
@@ -228,10 +228,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-classdesc.html">@classdesc</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-classdesc.html">@classdesc</a></li>
 </ul>
     </article>
     
@@ -244,3 +244,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-enum.html b/tags-enum.html
index 34977347..e8c40682 100644
--- a/tags-enum.html
+++ b/tags-enum.html
@@ -175,27 +175,27 @@
 	
 	<article>
 	<h1>@enum</h1>
-
-<h3>Syntax</h3>
-
-<code>@enum [&lt;type>]</code>
-
-<h3>Overview</h3>
-
-<p>
-    The @enum tag documents a collection of static properties whose values are all of the same type.
-</p>
-
-<p>
-    An enum is similar a collection of properties, except that an enum is documented in its own doc comment, whereas properties are documented within the doc comment of their container. Often this tag is used with @readonly, as an enum typically represents a collection of constants.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-    This shows how to document an object that represents a value with three possible states. Note that the enum members can have optional descriptions added if you wish. Also you can override the type, as is shown with "MAYBE" -- by default enum members will be documented with the same type as the enum itself.
-</p>
-
+
+<h3>Syntax</h3>
+
+<code>@enum [&lt;type>]</code>
+
+<h3>Overview</h3>
+
+<p>
+    The @enum tag documents a collection of static properties whose values are all of the same type.
+</p>
+
+<p>
+    An enum is similar a collection of properties, except that an enum is documented in its own doc comment, whereas properties are documented within the doc comment of their container. Often this tag is used with @readonly, as an enum typically represents a collection of constants.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+    This shows how to document an object that represents a value with three possible states. Note that the enum members can have optional descriptions added if you wish. Also you can override the type, as is shown with "MAYBE" -- by default enum members will be documented with the same type as the enum itself.
+</p>
+
 <dl class="example">
 <dt>A numeric enum, representing three states</dt>
 <dd>
@@ -215,10 +215,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-property.html">@property</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-property.html">@property</a></li>
 </ul>
     </article>
     
@@ -231,3 +231,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-event.html b/tags-event.html
index 250ab741..a455e690 100644
--- a/tags-event.html
+++ b/tags-event.html
@@ -175,42 +175,42 @@
 	
 	<article>
 	<h1>@event</h1>
-
-<h3>Syntax</h3>
-
-<code>@event &lt;className>#[event:]&lt;eventName></code>
-
-<h3>Overview</h3>
-
-<p>
-    The @event tag allows you to document an event that can be fired. A typical event is represented
-    by an object with a defined set of properties.
-</p>
-
-<p>
-    Once you have used the @event tag to define a specific type of event, you can use the @fires tag
-    to indicate that a method can fire that event.
-</p>
-
-<p>
-    JSDoc automatically prepends the namespace <code>event:</code> to each event's name. In general,
-    you must include this namespace when you link to the event in another doclet. (The @fires tag is
-    a notable exception; it allows you to omit the namespace.)
-</p>
-
-<p>
-    <strong>Note</strong>: JSDoc 3 uses @event doclets to document the content of an event. In
-    contrast, JSDoc Toolkit 2 used @event doclets to identify a function that can be fired when an
-    event of the same name occurs.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-    The following examples show how to document an event in the <code>Hurl</code> class called
-    <code>snowball</code>. The event contains an object with a single property.
-</p>
-
+
+<h3>Syntax</h3>
+
+<code>@event &lt;className>#[event:]&lt;eventName></code>
+
+<h3>Overview</h3>
+
+<p>
+    The @event tag allows you to document an event that can be fired. A typical event is represented
+    by an object with a defined set of properties.
+</p>
+
+<p>
+    Once you have used the @event tag to define a specific type of event, you can use the @fires tag
+    to indicate that a method can fire that event.
+</p>
+
+<p>
+    JSDoc automatically prepends the namespace <code>event:</code> to each event's name. In general,
+    you must include this namespace when you link to the event in another doclet. (The @fires tag is
+    a notable exception; it allows you to omit the namespace.)
+</p>
+
+<p>
+    <strong>Note</strong>: JSDoc 3 uses @event doclets to document the content of an event. In
+    contrast, JSDoc Toolkit 2 used @event doclets to identify a function that can be fired when an
+    event of the same name occurs.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+    The following examples show how to document an event in the <code>Hurl</code> class called
+    <code>snowball</code>. The event contains an object with a single property.
+</p>
+
 <dl class="example">
 <dt>Documenting a function call as an event</dt>
 <dd>
@@ -258,10 +258,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-fires.html">@fires</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-fires.html">@fires</a></li>
 </ul>
     </article>
     
@@ -274,3 +274,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-example.html b/tags-example.html
index 4b6b1957..4a3025df 100644
--- a/tags-example.html
+++ b/tags-example.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@example</h1>
-
-<h3>Overview</h3>
-
-<p>Provide an example of how to use a documented item. The text that follows this tag may span multiple lines, it will be displayed as highlighted code. The leading stars in the comment do not have to be present for this to work.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>Provide an example of how to use a documented item. The text that follows this tag may span multiple lines, it will be displayed as highlighted code. The leading stars in the comment do not have to be present for this to work.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Documenting examples.</dt>
 <dd>
@@ -220,10 +220,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -236,3 +236,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-exports.html b/tags-exports.html
index 6373cedc..050f07b0 100644
--- a/tags-exports.html
+++ b/tags-exports.html
@@ -175,19 +175,19 @@
 	
 	<article>
 	<h1>@exports</h1>
-
-<h3>Overview</h3>
-
-<p>
-Use the <code>@exports</code> tag when documenting JavaScript modules to indicate that an object is being exported.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-In cases where you are using the special "exports" namespace, the <code>@exports</code> tag is never needed...
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+Use the <code>@exports</code> tag when documenting JavaScript modules to indicate that an object is being exported.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+In cases where you are using the special "exports" namespace, the <code>@exports</code> tag is never needed...
+</p>
+
 <dl class="example">
 <dt>In CommonJS modules the exports namespace is understood by JSDoc 3</dt>
 <dd>
@@ -254,10 +254,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><p>
-If you are exporting an object named anything other than "exports", use the <code>@exports</code> tag to indicate what is being exported.
-</p>
-
+</dl><p>
+If you are exporting an object named anything other than "exports", use the <code>@exports</code> tag to indicate what is being exported.
+</p>
+
 <dl class="example">
 <dt>The @exports tag is used to document that the &quot;ns&quot; namespace is being exported</dt>
 <dd>
@@ -280,11 +280,11 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-module.html">@module</a></li>
-    <li><a href="howto-commonjs-modules.html">Documenting JavaScript modules with JSDoc 3</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-module.html">@module</a></li>
+    <li><a href="howto-commonjs-modules.html">Documenting JavaScript modules with JSDoc 3</a></li>
 </ul>
     </article>
     
@@ -297,3 +297,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-file.html b/tags-file.html
index 79b80ce0..1501944d 100644
--- a/tags-file.html
+++ b/tags-file.html
@@ -175,19 +175,19 @@
 	
 	<article>
 	<h1>@file</h1>
-
-<h3>Overview</h3>
-
-<p>Gives a description of the file. Place the comment at the top of the file. 
-The text following the @file tag will be used as the description of the file 
-in the default template.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>Gives a description of the file. Place the comment at the top of the file. 
+The text following the @file tag will be used as the description of the file 
+in the default template.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Giving an overview of a file</dt>
 <dd>
@@ -200,17 +200,17 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-version.html">@version</a></li>
-    <li><a href="tags-author.html">@author</a></li>
-</ul
-
-<h5>Contributers to these docs</h5>
-
-<ul>
-    <li><a href="https://github.com/matthewkastor">matthewkastor</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-version.html">@version</a></li>
+    <li><a href="tags-author.html">@author</a></li>
+</ul
+
+<h5>Contributers to these docs</h5>
+
+<ul>
+    <li><a href="https://github.com/matthewkastor">matthewkastor</a></li>
 </ul>
     </article>
     
@@ -223,3 +223,4 @@ <h5>Contributers to these docs</h5>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-fires.html b/tags-fires.html
index 891d9e2f..37e8ee7a 100644
--- a/tags-fires.html
+++ b/tags-fires.html
@@ -175,20 +175,20 @@
 	
 	<article>
 	<h1>@fires</h1>
-
-<h3>Syntax</h3>
-
-<code>@fires &lt;className>#[event:]&lt;eventName></code>
-
-<h3>Overview</h3>
-
-<p>
-    The @fires tag indicates that a method can fire a specified type of event when it is called. Use
-    the @event tag to document the event's content.
-</p>
-
-<h3>Examples</h3>
-
+
+<h3>Syntax</h3>
+
+<code>@fires &lt;className>#[event:]&lt;eventName></code>
+
+<h3>Overview</h3>
+
+<p>
+    The @fires tag indicates that a method can fire a specified type of event when it is called. Use
+    the @event tag to document the event's content.
+</p>
+
+<h3>Examples</h3>
+
 <dl class="example">
 <dt>Method that fires a &#39;drain&#39; event</dt>
 <dd>
@@ -204,10 +204,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-event.html">@event</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-event.html">@event</a></li>
 </ul>
     </article>
     
@@ -220,3 +220,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-global.html b/tags-global.html
index ba865957..109c9b84 100644
--- a/tags-global.html
+++ b/tags-global.html
@@ -175,19 +175,19 @@
 	
 	<article>
 	<h1>@global</h1>
-
-<h3>Overview</h3>
-
-<p>
-In cases where the static analysis feature of JSDoc is not able to derive the scope that you intend purely from the code surrounding your doc comments, you can use the @global tag to explicitly specify that a symbol should appear in the documentation as a <em>global</em> symbol.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-Use the @global tag to specify that a symbol should be documented as global.
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+In cases where the static analysis feature of JSDoc is not able to derive the scope that you intend purely from the code surrounding your doc comments, you can use the @global tag to explicitly specify that a symbol should appear in the documentation as a <em>global</em> symbol.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+Use the @global tag to specify that a symbol should be documented as global.
+</p>
+
 <dl class="example">
 <dt>Document an inner variable as a global</dt>
 <dd>
@@ -213,3 +213,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-ignore.html b/tags-ignore.html
index 8a613b3a..aaa37d9c 100644
--- a/tags-ignore.html
+++ b/tags-ignore.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@ignore</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-inner.html b/tags-inner.html
index ef92cc3a..a01b6dc6 100644
--- a/tags-inner.html
+++ b/tags-inner.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@inner</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-instance.html b/tags-instance.html
index 15de5667..675825d7 100644
--- a/tags-instance.html
+++ b/tags-instance.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@instance</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-kind.html b/tags-kind.html
index 0fa238f5..0962c2a9 100644
--- a/tags-kind.html
+++ b/tags-kind.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@kind</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-license.html b/tags-license.html
index 1c134b8d..a29b298c 100644
--- a/tags-license.html
+++ b/tags-license.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@license</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-member.html b/tags-member.html
index 246b76ab..ceae8349 100644
--- a/tags-member.html
+++ b/tags-member.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@member</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-memberof.html b/tags-memberof.html
index 4b1a7ee4..f4a5907e 100644
--- a/tags-memberof.html
+++ b/tags-memberof.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@memberof</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-method.html b/tags-method.html
index 6e5bf064..5a5f9881 100644
--- a/tags-method.html
+++ b/tags-method.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@method</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-mixes.html b/tags-mixes.html
index 85ad8480..27f3aa70 100644
--- a/tags-mixes.html
+++ b/tags-mixes.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@mixes</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-mixin.html b/tags-mixin.html
index 005723b7..4720723b 100644
--- a/tags-mixin.html
+++ b/tags-mixin.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@mixin</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-module.html b/tags-module.html
index 896d4bc6..b23ab002 100644
--- a/tags-module.html
+++ b/tags-module.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@module</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-name.html b/tags-name.html
index a1c10500..243dc36a 100644
--- a/tags-name.html
+++ b/tags-name.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@name</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-namespace.html b/tags-namespace.html
index 2724b334..c68e139f 100644
--- a/tags-namespace.html
+++ b/tags-namespace.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@namespace</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-param.html b/tags-param.html
index c43adf01..08a294c6 100644
--- a/tags-param.html
+++ b/tags-param.html
@@ -175,27 +175,27 @@
 	
 	<article>
 	<h1>@param</h1>
-
-
-<h3>Synonyms</h3>
-
-<ul>
-    <li>@arg</li>
-    <li>@argument</li>
-</ul>
-
-<h3>Overview</h3>
-
-<p>
-The @param tag (or @arg or @argument) documents a parameter of a function.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-The following examples show the basic usage of @param.
-</p>
-
+
+
+<h3>Synonyms</h3>
+
+<ul>
+    <li>@arg</li>
+    <li>@argument</li>
+</ul>
+
+<h3>Overview</h3>
+
+<p>
+The @param tag (or @arg or @argument) documents a parameter of a function.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+The following examples show the basic usage of @param.
+</p>
+
 <dl class="example">
 <dt>Basic usage of @param</dt>
 <dd>
@@ -235,10 +235,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><p>
-The following examples show how to indicate that a parameter can be optional and has a default value
-</p>
-
+</dl><p>
+The following examples show how to indicate that a parameter can be optional and has a default value
+</p>
+
 <dl class="example">
 <dt>An optional parameter</dt>
 <dd>
@@ -271,10 +271,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><p>
-A parameter could also have several types instead of just one. It can also be used multiple times. The following examples reflect these situations.
-</p>
-
+</dl><p>
+A parameter could also have several types instead of just one. It can also be used multiple times. The following examples reflect these situations.
+</p>
+
 <dl class="example">
 <dt>Multiple types</dt>
 <dd>
@@ -311,17 +311,17 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-returns.html">@returns</a></li>
-</ul>
-
-<h5>Contributers to these docs</h5>
-
-<ul>
-    <li><a href="https://github.com/customcommander">customcommander</a></li>
-</ul>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-returns.html">@returns</a></li>
+</ul>
+
+<h5>Contributers to these docs</h5>
+
+<ul>
+    <li><a href="https://github.com/customcommander">customcommander</a></li>
+</ul>
 
     </article>
     
@@ -334,3 +334,4 @@ <h5>Contributers to these docs</h5>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-private.html b/tags-private.html
index 5e4604ac..ff6c6451 100644
--- a/tags-private.html
+++ b/tags-private.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@private</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-property.html b/tags-property.html
index a9424d63..1b720c12 100644
--- a/tags-property.html
+++ b/tags-property.html
@@ -175,27 +175,27 @@
 	
 	<article>
 	<h1>@property</h1>
-
-<h3>Overview</h3>
-
-<p>
-    The @property tag is a way to easily document a list of static properties of a class, namespace or other object.
-</p>
-
-<p>
-    Normally JSDoc templates would create an entire new page to display information about each level of a nested namespace hierarchy. Sometimes what you really want is to just list all the properties, including nested properties, all together on the same page.
-</p>
-
-<p>
-    Note that property tags must be used in doc comments for the thing that they are properties of, a namespace or a class for example. This tag is intended for simple collections of static properties, it does not allow you to provide @examples or similar complex information for each property, just the type, name and description.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-    In this example we have a namespace named "config." We want all the information about the defaults property, including it's nested values to appear on the same page with the documentation for config.
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+    The @property tag is a way to easily document a list of static properties of a class, namespace or other object.
+</p>
+
+<p>
+    Normally JSDoc templates would create an entire new page to display information about each level of a nested namespace hierarchy. Sometimes what you really want is to just list all the properties, including nested properties, all together on the same page.
+</p>
+
+<p>
+    Note that property tags must be used in doc comments for the thing that they are properties of, a namespace or a class for example. This tag is intended for simple collections of static properties, it does not allow you to provide @examples or similar complex information for each property, just the type, name and description.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+    In this example we have a namespace named "config." We want all the information about the defaults property, including it's nested values to appear on the same page with the documentation for config.
+</p>
+
 <dl class="example">
 <dt>A namespace with defaults and nested default properties</dt>
 <dd>
@@ -220,11 +220,11 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li>Contrast this tag with the <a href="tags-member.html">@member</a> tag.</li>
-    <li><a href="tags-enum.html">@enum</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li>Contrast this tag with the <a href="tags-member.html">@member</a> tag.</li>
+    <li><a href="tags-enum.html">@enum</a></li>
 </ul>
     </article>
     
@@ -237,3 +237,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-protected.html b/tags-protected.html
index a787895f..ce1f7d16 100644
--- a/tags-protected.html
+++ b/tags-protected.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@protected</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-public.html b/tags-public.html
index 35f2d569..27ed31eb 100644
--- a/tags-public.html
+++ b/tags-public.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@public</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-readonly.html b/tags-readonly.html
index b6d37114..2844cdbe 100644
--- a/tags-readonly.html
+++ b/tags-readonly.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@readonly</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-requires.html b/tags-requires.html
index 09c74a32..4e4671cb 100644
--- a/tags-requires.html
+++ b/tags-requires.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@requires</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-returns.html b/tags-returns.html
index b7fed471..e54f2cf5 100644
--- a/tags-returns.html
+++ b/tags-returns.html
@@ -175,15 +175,15 @@
 	
 	<article>
 	<h1>@returns</h1>
-
-<h3>Overview</h3>
-
-<p>
-The @returns tag documents the value that a function returns.
-</p>
-
-<h3>Examples</h3>
-
+
+<h3>Overview</h3>
+
+<p>
+The @returns tag documents the value that a function returns.
+</p>
+
+<h3>Examples</h3>
+
 <dl class="example">
 <dt>Type of the return value</dt>
 <dd>
@@ -236,16 +236,16 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-param.html">@param</a></li>
-</ul>
-
-<h5>Contributers to these docs</h5>
-
-<ul>
-    <li><a href="https://github.com/customcommander">customcommander</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-param.html">@param</a></li>
+</ul>
+
+<h5>Contributers to these docs</h5>
+
+<ul>
+    <li><a href="https://github.com/customcommander">customcommander</a></li>
 </ul>
     </article>
     
@@ -258,3 +258,4 @@ <h5>Contributers to these docs</h5>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-see.html b/tags-see.html
index caf3ab3b..d4cc8a89 100644
--- a/tags-see.html
+++ b/tags-see.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@see</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-since.html b/tags-since.html
index 5cb709c6..1fd44325 100644
--- a/tags-since.html
+++ b/tags-since.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@since</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-summary.html b/tags-summary.html
index 966fe6d3..c7fb7cfb 100644
--- a/tags-summary.html
+++ b/tags-summary.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@summary</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-this.html b/tags-this.html
index ae523b33..4bcf1e07 100644
--- a/tags-this.html
+++ b/tags-this.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@this</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-throws.html b/tags-throws.html
index 4e71af82..ea477420 100644
--- a/tags-throws.html
+++ b/tags-throws.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@throws</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-todo.html b/tags-todo.html
index 41399580..2ccda813 100644
--- a/tags-todo.html
+++ b/tags-todo.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@todo</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-tutorial.html b/tags-tutorial.html
index f2b8f8c5..d2df2cb6 100644
--- a/tags-tutorial.html
+++ b/tags-tutorial.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@tutorial</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-type.html b/tags-type.html
index 27e65c06..d693a27f 100644
--- a/tags-type.html
+++ b/tags-type.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@type</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-typedef.html b/tags-typedef.html
index 38124c74..473da586 100644
--- a/tags-typedef.html
+++ b/tags-typedef.html
@@ -175,17 +175,17 @@
 	
 	<article>
 	<h1>@typedef</h1>
-
-<h3>Overview</h3>
-
-<p>
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Example goes here</dt>
 <dd>
@@ -194,10 +194,10 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="#">...</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="#">...</a></li>
 </ul>
     </article>
     
@@ -210,3 +210,4 @@ <h3>Examples</h3>
 	<script>prettyPrint()</script>
 </body>
 </html>
+
diff --git a/tags-version.html b/tags-version.html
index eefba2ad..32b6ad67 100644
--- a/tags-version.html
+++ b/tags-version.html
@@ -175,18 +175,18 @@
 	
 	<article>
 	<h1>@version</h1>
-
-<h3>Overview</h3>
-
-<p>Documents the version of an item. The text following the @version tag 
-will be used to denote the version of the item.
-</p>
-
-<h3>Examples</h3>
-
-<p>
-</p>
-
+
+<h3>Overview</h3>
+
+<p>Documents the version of an item. The text following the @version tag 
+will be used to denote the version of the item.
+</p>
+
+<h3>Examples</h3>
+
+<p>
+</p>
+
 <dl class="example">
 <dt>Documenting an item&#39;s version.</dt>
 <dd>
@@ -203,17 +203,17 @@ <h3>Examples</h3>
 
 </pre>
 </dd>
-</dl><h3>See Also</h3>
-
-<ul>
-    <li><a href="tags-author.html">@author</a></li>
-	<li><a href="tags-tutorial.html">@tutorial</a></li>
-</ul>
-
-<h5>Contributers to these docs</h5>
-
-<ul>
-    <li><a href="https://github.com/matthewkastor">matthewkastor</a></li>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-author.html">@author</a></li>
+	<li><a href="tags-tutorial.html">@tutorial</a></li>
+</ul>
+
+<h5>Contributers to these docs</h5>
+
+<ul>
+    <li><a href="https://github.com/matthewkastor">matthewkastor</a></li>
 </ul>
     </article>
     
@@ -226,3 +226,4 @@ <h5>Contributers to these docs</h5>
 	<script>prettyPrint()</script>
 </body>
 </html>
+

From 3a12df92c83024da97093c1fb5395a609fda2521 Mon Sep 17 00:00:00 2001
From: Philip Peitsch <philip.peitsch@gmail.com>
Date: Tue, 29 Jan 2013 22:46:09 +1100
Subject: [PATCH 3/5] Ported original documentation from
 http://code.google.com/p/jsdoc-toolkit/wiki/TagLends

---
 Jake/articles/tags-lends | 111 ++++++++++++++
 index.html               |   3 +-
 tags-lends.html          | 312 +++++++++++++++++++++++++++++++++++++++
 3 files changed, 425 insertions(+), 1 deletion(-)
 create mode 100644 Jake/articles/tags-lends
 create mode 100644 tags-lends.html

diff --git a/Jake/articles/tags-lends b/Jake/articles/tags-lends
new file mode 100644
index 00000000..45fe0a1d
--- /dev/null
+++ b/Jake/articles/tags-lends
@@ -0,0 +1,111 @@
+<!--{
+    "title":       "@lends",
+    "out":         "tags-lends.html",
+    "description": "Document properties on an object literal as if they belonged to an object with a given name"
+}-->
+<h3>Syntax</h3>
+
+<code>@lends &lt;namepath></code>
+
+<h3>Overview</h3>
+
+<p>
+	The <code>@lends</code> tag allows you to document all the members of an anonymous object literal as if they 
+	were members of an object with the given name. You might want to do this if you were passing an anonymous 
+	object literal into a function that creates a named class from its members
+</p>
+
+<h3>Examples</h3>
+
+<p>
+	In this example we want to use a helper function to make a class named "Person," along with instance 
+	methods named "initialize" and "say." This is similar to how some popular frameworks handle class creation.
+</p>
+
+{{#example}} Example class
+// we want to document this as being a class
+var Person = makeClass(
+    // we want to document these as being methods
+    {
+        initialize: function(name) {
+            this.name = name;
+        },
+        say: function(message) {
+            return this.name + " says: " + message;
+        }
+    }
+);
+{{/example}}
+
+<p>
+	Without any doc comments JsDoc Toolkit won't automatically recognize either a class named "Person" nor it's 
+	two methods. To document the methods we must use a "@lends" tag in a doc comment immediately before the 
+	object literal to tell JsDoc Toolkit that all the member names of that object literal are being "lent" to a 
+	variable named "Person."
+</p>
+
+{{#example}} Documented as static methods
+/** @class */
+var Person = makeClass(
+    /** @lends Person */
+    {
+        initialize: function(name) {
+            this.name = name;
+        },
+        say: function(message) {
+            return this.name + " says: " + message;
+        }
+    }
+);
+{{/example}}
+
+<p>
+	Now the functions named "initialize" and "say" will be documented, but they appear as static methods of an 
+	class named "Person." That is possibly what you meant, but in this case we want "initialize" and "say" to 
+	belong to the instances of the "Person" class. So we change things slightly by lending the methods to the 
+	class's prototype:
+</p>
+
+{{#example}} Documented as instance methods
+/** @class */
+var Person = makeClass(
+    /** @lends Person.prototype */
+    {
+        initialize: function(name) {
+            this.name = name;
+        },
+        say: function(message) {
+            return this.name + " says: " + message;
+        }
+    }
+);
+{{/example}}
+
+<p>
+	If you are using one of the lent functions to construct the class, you can mark it as such using the 
+	@constructs tag, but remember to remove the @class tag in that case, or else two @classes will be documented.
+</p>
+
+{{#example}} Documented constructor
+var Person = makeClass(
+    /**
+      @lends Person.prototype
+    */
+    {
+        /** @constructs */
+        initialize: function(name) {
+            this.name = name;
+        },
+        say: function(message) {
+            return this.name + " says: " + message;
+        }
+    }
+);
+{{/example}}
+
+<h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-borrows.html">@borrows</a></li>
+    <li><a href="tags-cnstructs.html">@constructs</a></li>
+</ul>
\ No newline at end of file
diff --git a/index.html b/index.html
index 05db006f..dfaac1f1 100644
--- a/index.html
+++ b/index.html
@@ -258,7 +258,8 @@ <h2 name="JSDoc3_Tag_Dictionary" id="JSDoc3_Tag_Dictionary">JSDoc 3 Tag Dictiona
 		<dd>[todo] Remove this from the final output.</dd>	<dt><a href="tags-inner.html">@inner</a></dt>
 		<dd>[todo] Document an inner object.</dd>	<dt><a href="tags-instance.html">@instance</a></dt>
 		<dd>[todo] Document an instance member.</dd>	<dt><a href="tags-kind.html">@kind</a></dt>
-		<dd>[todo] What kind of object is this?</dd>	<dt><a href="tags-license.html">@license</a></dt>
+		<dd>[todo] What kind of object is this?</dd>	<dt><a href="tags-lends.html">@lends</a></dt>
+		<dd>Document properties on an object literal as if they belonged to an object with a given name</dd>	<dt><a href="tags-license.html">@license</a></dt>
 		<dd>[todo] Document the software license that applies to this code.</dd>	<dt><a href="tags-member.html">@member</a></dt>
 		<dd>[todo] Document a member.</dd>	<dt><a href="tags-memberof.html">@memberof</a></dt>
 		<dd>[todo] This object is a member or another object.</dd>	<dt><a href="tags-method.html">@method</a></dt>
diff --git a/tags-lends.html b/tags-lends.html
new file mode 100644
index 00000000..f35526c3
--- /dev/null
+++ b/tags-lends.html
@@ -0,0 +1,312 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+	<meta charset="utf-8">
+	<meta name="description" content="Document properties on an object literal as if they belonged to an object with a given name"><title>Use JSDoc: @lends</title>
+	
+	<link rel="stylesheet" href="lib/prettify.css" />
+	<script src="lib/prettify.js"></script>
+	
+	<script type="text/javascript">
+	    /* Make HTML 5 elements stylable in IE */
+        document.createElement('header');
+        document.createElement('nav');
+        document.createElement('article');
+        document.createElement('footer');
+        document.createElement('hgroup');
+	</script>
+	
+	<style>
+		body 
+		{
+			font: 1em 'Helvetica Neue', Helvetica, Arial, sans-serif;
+			padding: 0;
+			margin: 0;
+		}
+		
+		a, a:visited, a:active 
+		{
+			color: #605C89;
+		}
+		
+		/* Make HTML 5 elements display block-level for consistent styling */
+		header, nav, article, footer, address 
+		{
+			display: block;
+		}
+		
+		header
+		{
+			background-color: #EBEBEB;
+			color: #006FBB;
+			margin: 0;
+			margin-bottom: 32px;
+			padding: 18px;
+			font-size: 2.4em;
+			font-weight: bold;
+			border-bottom: 1px #C6C6C6 solid;
+		}
+		
+		header a, header a:visited 
+		{
+		    color: #006FBB;
+			text-decoration: none;
+		}
+		
+		article 
+		{
+			margin: 18px;
+		}
+		
+		footer
+		{
+			margin: 16px;
+			margin-top: 32px;
+			font-style: italic;
+			font-size: 0.8em;
+		}
+		
+		h1, h2, h3, h4, h5, h6
+		{
+			color: #B93A38;
+		}
+		
+		h1
+		{
+			font-size: 1.428em;
+			text-indent: 0;
+		}
+
+		h2
+		{
+			font-size: 1.285em;
+			text-indent: 1%;
+		}
+
+		h3
+		{
+			font-size: 1.142em;
+			text-indent: 2%;
+		}
+
+		h4
+		{
+			font-size: 1em;
+			text-indent: 3%;
+		}
+
+		h5
+		{
+			font-size: 0.857em;
+			text-indent: 4%;
+		}
+
+		h6
+		{
+			font-size: 0.714em;
+			text-indent: 5%;
+		}
+		
+		p
+		{
+			text-indent: 2%;
+		}
+		
+		dl
+		{
+			margin-left: 2%;
+			padding-left: 0;
+		}
+		
+		dt
+		{
+			margin-left: 16px;
+			padding-left: 4px;
+			margin-top: 8px;
+		}
+		
+		dt a, dt a:visited 
+		{
+			color: #3E00B6;
+		}
+		
+		dd
+		{
+			margin-left: 16px;
+			padding-left: 4px;
+		}
+		
+		ol, ul
+		{
+			margin-left: 2%;
+		}
+		
+		code 
+		{
+			font: 1em Consolas, "Lucida Console", Monaco, monospace;
+			background-color: #DEDEDE;
+		}
+		
+		pre
+		{
+			display: block;
+			border: 1px solid #999;
+			margin: 12px;
+			padding: 8px;
+			white-space: pre-wrap;
+			background-color: #DEDEDE;
+		}
+		
+		.example dt 
+		{
+			font-weight: bold;
+		}
+
+	</style>
+</head>
+
+<body>
+	<header>
+	    <a href="./index.html">@use JSDoc</a>
+	</header>
+	
+	<nav>
+	</nav>
+	
+	<article>
+	<h1>@lends</h1>
+
+<h3>Syntax</h3>
+
+<code>@lends &lt;namepath></code>
+
+<h3>Overview</h3>
+
+<p>
+	The <code>@lends</code> tag allows you to document all the members of an anonymous object literal as if they 
+	were members of an object with the given name. You might want to do this if you were passing an anonymous 
+	object literal into a function that creates a named class from its members
+</p>
+
+<h3>Examples</h3>
+
+<p>
+	In this example we want to use a helper function to make a class named "Person," along with instance 
+	methods named "initialize" and "say." This is similar to how some popular frameworks handle class creation.
+</p>
+
+<dl class="example">
+<dt>Example class</dt>
+<dd>
+<pre class="prettyprint lang-js">
+// we want to document this as being a class
+var Person = makeClass(
+    // we want to document these as being methods
+    {
+        initialize: function(name) {
+            this.name = name;
+        },
+        say: function(message) {
+            return this.name + " says: " + message;
+        }
+    }
+);
+
+</pre>
+</dd>
+</dl><p>
+	Without any doc comments JsDoc Toolkit won't automatically recognize either a class named "Person" nor it's 
+	two methods. To document the methods we must use a "@lends" tag in a doc comment immediately before the 
+	object literal to tell JsDoc Toolkit that all the member names of that object literal are being "lent" to a 
+	variable named "Person."
+</p>
+
+<dl class="example">
+<dt>Documented as static methods</dt>
+<dd>
+<pre class="prettyprint lang-js">
+/** @class */
+var Person = makeClass(
+    /** @lends Person */
+    {
+        initialize: function(name) {
+            this.name = name;
+        },
+        say: function(message) {
+            return this.name + " says: " + message;
+        }
+    }
+);
+
+</pre>
+</dd>
+</dl><p>
+	Now the functions named "initialize" and "say" will be documented, but they appear as static methods of an 
+	class named "Person." That is possibly what you meant, but in this case we want "initialize" and "say" to 
+	belong to the instances of the "Person" class. So we change things slightly by lending the methods to the 
+	class's prototype:
+</p>
+
+<dl class="example">
+<dt>Documented as instance methods</dt>
+<dd>
+<pre class="prettyprint lang-js">
+/** @class */
+var Person = makeClass(
+    /** @lends Person.prototype */
+    {
+        initialize: function(name) {
+            this.name = name;
+        },
+        say: function(message) {
+            return this.name + " says: " + message;
+        }
+    }
+);
+
+</pre>
+</dd>
+</dl><p>
+	If you are using one of the lent functions to construct the class, you can mark it as such using the 
+	@constructs tag, but remember to remove the @class tag in that case, or else two @classes will be documented.
+</p>
+
+<dl class="example">
+<dt>Documented constructor</dt>
+<dd>
+<pre class="prettyprint lang-js">
+var Person = makeClass(
+    /**
+      @lends Person.prototype
+    */
+    {
+        /** @constructs */
+        initialize: function(name) {
+            this.name = name;
+        },
+        say: function(message) {
+            return this.name + " says: " + message;
+        }
+    }
+);
+
+</pre>
+</dd>
+</dl><h3>See Also</h3>
+
+<ul>
+    <li><a href="tags-borrows.html">@borrows</a></li>
+    <li><a href="tags-cnstructs.html">@constructs</a></li>
+</ul>
+    </article>
+    
+    <footer>
+        <img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-sa/3.0/80x15.png" /><br>
+        Copyright &#169; 2012 The <a href="https://github.com/jsdoc3/jsdoc3.github.com/contributors">contributors</a> to the JSDoc 3 documentation project.<br />
+        This site is <a href="https://github.com/jsdoc3/jsdoc3.github.com">open source</a> and licensed under the <a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-ShareAlike 3.0 Unported License</a>.
+	</footer>
+
+	<script>prettyPrint()</script>
+</body>
+</html>
+

From bea361ec7798a7f78def13a7d41286c69f1b5541 Mon Sep 17 00:00:00 2001
From: Philip Peitsch <philip.peitsch@gmail.com>
Date: Tue, 29 Jan 2013 23:03:19 +1100
Subject: [PATCH 4/5] Fixed type in @lend's See Also links

---
 Jake/articles/tags-lends | 2 +-
 tags-lends.html          | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Jake/articles/tags-lends b/Jake/articles/tags-lends
index 45fe0a1d..bae62030 100644
--- a/Jake/articles/tags-lends
+++ b/Jake/articles/tags-lends
@@ -107,5 +107,5 @@ var Person = makeClass(
 
 <ul>
     <li><a href="tags-borrows.html">@borrows</a></li>
-    <li><a href="tags-cnstructs.html">@constructs</a></li>
+    <li><a href="tags-constructs.html">@constructs</a></li>
 </ul>
\ No newline at end of file
diff --git a/tags-lends.html b/tags-lends.html
index f35526c3..a10ecc41 100644
--- a/tags-lends.html
+++ b/tags-lends.html
@@ -296,7 +296,7 @@ <h3>Examples</h3>
 
 <ul>
     <li><a href="tags-borrows.html">@borrows</a></li>
-    <li><a href="tags-cnstructs.html">@constructs</a></li>
+    <li><a href="tags-constructs.html">@constructs</a></li>
 </ul>
     </article>
     

From e8b7e654be253c0f040739d1c6b0bb64090a2ac0 Mon Sep 17 00:00:00 2001
From: Philip Peitsch <p.peitsch@qsr.com.au>
Date: Fri, 1 Feb 2013 09:14:28 +1100
Subject: [PATCH 5/5] Corrected JSDoc project name references

---
 Jake/articles/tags-lends | 4 ++--
 tags-lends.html          | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/Jake/articles/tags-lends b/Jake/articles/tags-lends
index bae62030..d276851d 100644
--- a/Jake/articles/tags-lends
+++ b/Jake/articles/tags-lends
@@ -38,9 +38,9 @@ var Person = makeClass(
 {{/example}}
 
 <p>
-	Without any doc comments JsDoc Toolkit won't automatically recognize either a class named "Person" nor it's 
+	Without any doc comments JSDoc won't automatically recognize either a class named "Person" nor it's 
 	two methods. To document the methods we must use a "@lends" tag in a doc comment immediately before the 
-	object literal to tell JsDoc Toolkit that all the member names of that object literal are being "lent" to a 
+	object literal to tell JSDoc that all the member names of that object literal are being "lent" to a 
 	variable named "Person."
 </p>
 
diff --git a/tags-lends.html b/tags-lends.html
index a10ecc41..1a6e74c6 100644
--- a/tags-lends.html
+++ b/tags-lends.html
@@ -215,9 +215,9 @@ <h3>Examples</h3>
 </pre>
 </dd>
 </dl><p>
-	Without any doc comments JsDoc Toolkit won't automatically recognize either a class named "Person" nor it's 
+	Without any doc comments JSDoc won't automatically recognize either a class named "Person" nor it's 
 	two methods. To document the methods we must use a "@lends" tag in a doc comment immediately before the 
-	object literal to tell JsDoc Toolkit that all the member names of that object literal are being "lent" to a 
+	object literal to tell JSDoc that all the member names of that object literal are being "lent" to a 
 	variable named "Person."
 </p>
 
