docs: generate docs

Author: brettz9

README.md

@@ -3396,17 +3396,19 @@ const language = {
 
 Requires all types to be valid JSDoc or Closure compiler types without syntax errors.
 
-Also impacts behaviors on namepath-pointing or event-pointing tags:
+Also impacts behaviors on namepath (or event)-defining and pointing tags:
 
-1.  `@alias`, `@augments`, `@extends`, `@lends`, `@memberof`, `@memberof!`, `@mixes`, `@name`, `@this`
-1.  `@callback`, `@event`, `@listens`, `@fires`, `@emits`
-1.  `@borrows`
+1. Name(path)-defining tags: `@class`, `@constructor`, `@constant`, `@const`, `@external`, `@host`, `@function`, `@func`, `@method`, `@interface`, `@member`, `@var`, `@mixin`, `@name`, `@namespace`, `@typedef`
+1. Name(path)-pointing tags: `@alias`, `@augments`, `@extends`, `@lends`, `@memberof`, `@memberof!`, `@mixes`, `@this`
+1. Name(path)-defining tags (which may have value without namepath): `@callback`, `@event`
+1. Name(path)-pointing tags (which may have value without namepath): `@listens`, `@fires`, `@emits`
+1. Name(path)-pointing tags (multiple names in one): `@borrows`
 
 The following apply to the above sets:
 
--   Expect tags in set 1 or 2 to have a valid namepath if present
--   Prevent set 2 from being empty by setting `allowEmptyNamepaths` to `false` as these tags might have some indicative value without a path (but set 1 will always fail if empty)
--   For the special case of set 3, i.e., `@borrows <that namepath> as <this namepath>`, check that both namepaths are present and valid and ensure there is an `as ` between them.
+- Expect tags in set 1-4 to have a valid namepath if present
+- Prevent sets 3-4 from being empty by setting `allowEmptyNamepaths` to `false` as these tags might have some indicative value without a path (but sets 1-2 will always fail if empty)
+- For the special case of set 5, i.e., `@borrows <that namepath> as <this namepath>`, check that both namepaths are present and valid and ensure there is an `as ` between them.
 
 |||
 |---|---|