fix(docs): fix typos and doc link formatting in documentation #5092 (#5093)

This Pull Request fixes/closes #5092.

It changes the following:

- **core/parser/src/parser/statement/declaration/mod.rs** — Put the
`[spec]` doc link on its own line so it is no longer concatenated with
`mod export;`.
- **core/runtime/src/fetch/request.rs** — Add missing space in doc link:
`[mdn]:https://` → `[mdn]: https://` for CommonMark compliance.
- **docs/vm.md** — Fix typo: "binarys" → "binaries" in the VM debugging
documentation.
- **core/engine/src/vm/call_frame/mod.rs** — Fix grammar: "a integer" →
"an integer" in unreachable messages (2 places).
- **core/engine/src/vm/runtime_limits.rs** — Fix grammar: "throw and
error" → "throw an error" in doc comments (2 places).

All changes are documentation and comments only; no behavior changes.

Author: Mayank Raj

core/engine/src/vm/call_frame/mod.rs

@@ -256,10 +256,10 @@ impl JsValue {
                 0 => return GeneratorResumeKind::Normal,
                 1 => return GeneratorResumeKind::Throw,
                 2 => return GeneratorResumeKind::Return,
-                _ => unreachable!("generator kind must be a integer between 1..=2, got {value}"),
+                _ => unreachable!("generator kind must be an integer between 1..=2, got {value}"),
             }
         }
 
-        unreachable!("generator kind must be a integer type")
+        unreachable!("generator kind must be an integer type")
     }
 }

core/engine/src/vm/runtime_limits.rs

@@ -29,7 +29,7 @@ impl Default for RuntimeLimits {
 impl RuntimeLimits {
     /// Return the loop iteration limit.
     ///
-    /// If the limit is exceeded in a loop it will throw and error.
+    /// If the limit is exceeded in a loop it will throw an error.
     ///
     /// The limit value [`u64::MAX`] means that there is no limit.
     #[inline]
@@ -40,7 +40,7 @@ impl RuntimeLimits {
 
     /// Set the loop iteration limit.
     ///
-    /// If the limit is exceeded in a loop it will throw and error.
+    /// If the limit is exceeded in a loop it will throw an error.
     ///
     /// Setting the limit to [`u64::MAX`] means that there is no limit.
     #[inline]

core/parser/src/parser/statement/declaration/mod.rs

@@ -5,7 +5,7 @@
 //!  - [ECMAScript specification][spec]
 //!
 //! [mdn]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements#Declarations
-//! [spec]:https://tc39.es/ecma262/#sec-declarations-and-the-variable-statement
+//! [spec]: https://tc39.es/ecma262/#sec-declarations-and-the-variable-statement
 
 mod export;
 mod hoistable;

core/runtime/src/fetch/request.rs

@@ -46,7 +46,7 @@ type VecOrMap<K, V> = Either<Vec<(K, V)>, BTreeMap<K, V>>;
 /// A [RequestInit][mdn] object. This is a JavaScript object (not a
 /// class) that can be used as options for creating a [`JsRequest`].
 ///
-/// [mdn]:https://developer.mozilla.org/en-US/docs/Web/API/RequestInit
+/// [mdn]: https://developer.mozilla.org/en-US/docs/Web/API/RequestInit
 // TODO: This class does not contain all fields that are defined in the spec.
 #[derive(Debug, Clone, TryFromJs, Trace, Finalize)]
 pub struct RequestInit {

docs/vm.md

@@ -394,7 +394,7 @@ The above output contains the following information:
 
 ### Comparing Bytecode output
 
-If you wanted another engine's bytecode output for the same JS, SpiderMonkey's bytecode output is the best to use. You can follow the setup [here](https://udn.realityripple.com/docs/Mozilla/Projects/SpiderMonkey/Introduction_to_the_JavaScript_shell). You will need to build from source because the pre-built binarys don't include the debugging utilities which we need.
+If you wanted another engine's bytecode output for the same JS, SpiderMonkey's bytecode output is the best to use. You can follow the setup [here](https://udn.realityripple.com/docs/Mozilla/Projects/SpiderMonkey/Introduction_to_the_JavaScript_shell). You will need to build from source because the pre-built binaries don't include the debugging utilities which we need.
 
 I named the binary `js_shell` as `js` conflicts with NodeJS. Once up and running you should be able to use `js_shell -f tests/js/test.js`. You will get no output to begin with, this is because you need to run `dis()` or `dis([func])` in the code. Once you've done that you should get some output like so: