manual: fix release notes

fix key spelling errors, type errors, things-should-not-be-comments errors

Change-Id: I3ce12873aa78002bca686bd88404771895b05d30

doc/manual/rl-next/debugger-locals-for-let-expressions.md

@@ -1,7 +1,7 @@
 ---
 synopsis: "`--debugger` can now access bindings from `let` expressions"
 prs: 9918
-issues: 8827.
+issues: 8827
 ---
 
 Breakpoints and errors in the bindings of a `let` expression can now access

doc/manual/rl-next/empty-search-regex.md

@@ -1,8 +1,6 @@
+---
 synopsis: Disallow empty search regex in `nix search`
-prs: #9481
-description: {
+prs: 9481
+---
 
 [`nix search`](@docroot@/command-ref/new-cli/nix3-search.md) now requires a search regex to be passed. To show all packages, use `^`.
-
-}
-

doc/manual/rl-next/nix-flake-update-ux.md

@@ -1,5 +1,5 @@
 ---
-synposis: "`Overhaul `nix flake update` and `nix flake lock` UX"
+synopsis: "`Overhaul `nix flake update` and `nix flake lock` UX"
 prs: 8817
 ---
 

doc/manual/rl-next/print-value-in-coercion-error.md

@@ -1,7 +1,7 @@
 ---
 synopsis: Coercion errors include the failing value
-issues: #561
-prs: #9754
+issues: 561
+prs: 9754
 ---
 
 The `error: cannot coerce a <TYPE> to a string` message now includes the value

doc/manual/rl-next/print-value-in-type-error.md

@@ -1,7 +1,7 @@
 ---
 synopsis: Type errors include the failing value
-issues: #561
-prs: #9753
+issues: 561
+prs: 9753
 ---
 
 In errors like `value is an integer while a list was expected`, the message now