refactor(ext): align error messages (#25914)

Aligns the error messages in the ext folder to be in-line with the Deno
style guide.

https://github.com/denoland/deno/issues/25269

<!--
Before submitting a PR, please read
https://docs.deno.com/runtime/manual/references/contributing

1. Give the PR a descriptive title.

  Examples of good title:
    - fix(std/http): Fix race condition in server
    - docs(console): Update docstrings
    - feat(doc): Handle nested reexports

  Examples of bad title:
    - fix #7123
    - update docs
    - fix bugs

2. Ensure there is a related issue and it is referenced in the PR text.
3. Ensure there are tests that cover the changes.
4. Ensure `cargo test` passes.
5. Ensure `./tools/format.js` passes without changing files.
6. Ensure `./tools/lint.js` passes.
7. Open as a draft PR if your work is still in progress. The CI won't
run
   all steps, but you can add '[ci]' to a commit message to force it to.
8. If you would like to run the benchmarks on the CI, add the 'ci-bench'
label.
-->

1 files changed, 1 insertions, 1 deletions

diff --git a/ext/url/00_url.js b/ext/url/00_url.js
index 577caba90..ec875da76 100644
--- a/ext/url/00_url.js
+++ b/ext/url/00_url.js
@@ -139,7 +139,7 @@ class URLSearchParams {
           throw new TypeError(
             `${prefix}: Item ${
               i + 0
-            } in the parameter list does have length 2 exactly.`,
+            } in the parameter list does have length 2 exactly`,
           );
         }
         return [pair[0], pair[1]];