docs: fix notes placement and update description

Signed-off-by: Athan <[email protected]>

Author: kgryte

lib/node_modules/@stdlib/_tools/eslint/rules/tsdoc-declarations-doctest/README.md

@@ -38,7 +38,7 @@ var rule = require( '@stdlib/_tools/eslint/rules/tsdoc-declarations-doctest' );
 
 #### rule
 
-[ESLint rule][eslint-rules] to ensure that return annotations in TSDoc examples match the actual output in TypeScript declaration files (`*.d.ts`). Return annotations may start with `returns`, `throws`, or `=>`. `returns` follow variable declarations or assignment expressions, whereas `=>` follow expression-only forms including `console.log` calls. The rule validates `@example` blocks in TSDoc comments within `.d.ts` files by automatically resolving the corresponding implementation via the nearest `package.json` file.
+[ESLint rule][eslint-rules] to ensure that return annotations in TSDoc examples match the actual output in TypeScript declaration files (`*.d.ts`).
 
 **Bad**:
 
@@ -84,6 +84,20 @@ export = add;
 
 <!-- /.usage -->
 
+<section class="notes">
+
+## Notes
+
+-   Return annotations may start with `returns`, `throws`, or `=>`. `returns` follow variable declarations or assignment expressions, whereas `=>` follow expression-only forms including `console.log` calls.
+-   The rule validates `@example` blocks in TSDoc comments within `*.d.ts` files by resolving the corresponding implementation via the nearest `package.json` file in the same or a parent directory and using its `main` field.
+-   The rule skips validation if the `package.json` file cannot be found or if the resolved implementation cannot be loaded.
+-   Examples are executed in a sandboxed VM context with limited globals for security.
+-   This rule is specifically designed for TypeScript declaration files and will only process files with a `*.d.ts` filename extension.
+
+</section>
+
+<!-- /.notes -->
+
 <section class="examples">
 
 ## Examples
@@ -151,19 +165,6 @@ var result = linter.verify( code, {
 
 <!-- /.examples -->
 
-<section class="notes">
-
-## Notes
-
--   The rule automatically resolves the implementation path by traversing up the directory tree to find the nearest `package.json` file and using its `main` field.
--   The rule skips validation if the `package.json` file cannot be found or if the resolved implementation cannot be loaded.
--   Examples are executed in a sandboxed VM context with limited globals for security.
--   This rule is specifically designed for TypeScript declaration files and will only process files with a `.d.ts` extension.
-
-</section>
-
-<!-- /.notes -->
-
 <!-- Section for related `stdlib` packages. Do not manually edit this section, as it is automatically populated. -->
 
 <section class="related">