Fix review comments

Author: maartenba

.github/instructions/docs.instructions.md

@@ -24,7 +24,7 @@ Review documentation for Duende Software products (IdentityServer, BFF, etc.). F
 
 ## Frontmatter
 
-* Must have `title`, `description`, and `date` (YYYY-MM-DD format).
+* Must have `title`, `description`, and `date`. Prefer `YYYY-MM-DD`, but do not flag other Astro/Starlight-accepted date formats already used in this repo (for example, full ISO 8601 timestamps).
 * May have `sidebar` with `label` and `order`. For long `title`, the `label` is used as a shorter entry in the navigation bar, and should be shorter than `title`.
 
 ## Linking Rules
@@ -33,7 +33,7 @@ Review documentation for Duende Software products (IdentityServer, BFF, etc.). F
 * Internal links must start at the content root (e.g. `/identityserver/troubleshooting/index.md`) and include the `.md` or `.mdx` extension.
 * External links must use HTTPS.
 * Link relevant text: prefer `learn more about [improving sign-in]` over `click [here]`.
-* Long links (75+ chars) or repeated links should use reference-style links/link definitions at the bottom of the file (for example, `[label]: https://example.com`).
+* Long links (75+ chars) or repeated links should use markdown anchor syntax at the bottom of the file.
 * When linking externally, include a sentence about what the reader will find.
 
 ## Markdown Style
@@ -44,14 +44,14 @@ Review documentation for Duende Software products (IdentityServer, BFF, etc.). F
 
 ## Code Blocks
 
-* Use triple backticks with a language identifier (`csharp`, `bash`, `json`, `html`, `javascript`, `typescript`, `css`).
+* Use triple backticks with an appropriate language identifier. Common identifiers used in this repo include `csharp`, `bash`, `powershell`, `shell`, `sh`, `json`, `html`, `javascript`, `typescript`, `css`, `razor`, `xml`, `sql`, `sqlite`, `txt`, `diff`, and `mermaid`.
 * Prefer `csharp` over `cs` for C#.
 * Add a title as a comment in the first line (e.g. `// Program.cs`).
 * Code should not require horizontal scrolling — keep it concise.
 * C# examples should use latest syntax (top-level statements, collection expressions).
 * Examples should be runnable and complete — "copy-paste from docs" is the goal.
 * Use backticks for inline references to properties, classes, symbols, and values (including HTTP status codes like `404`).
-* Code blocks must start at column 0 with no excessive leading whitespace.
+* Avoid excessive indentation in code blocks; use column 0 unless indentation is needed to nest under lists or MDX components.
 * Mention NuGet packages with `dotnet add package ...` in a `bash` block and link to the NuGet Gallery.
 
 ## Redirects

README.md

@@ -140,12 +140,11 @@ WebStorm has Grazie as a built-in spell checker and grammar checker, and support
 * Use `*` for lists. Do not use `-`.
 * Use `[link title](https://example.com)` for links, avoid reference-style links unless you need to repeat the same link multiple times.
 * For internal links, always include the extension (e.g. `.md` or `.mdx`)
-* Prefer `csharp` over `cs` to set the language for C# code blocks.
 
 ### Code Block Style
 
-* Use triple backticks to enclose code blocks.
-* Use a language identifier to specify the language (e.g. `csharp`, `bash`, `json`, `html`, `javascript`, `typescript`, `css`, `json`)
+* Use triple backticks with an appropriate language identifier. Common identifiers used in this repo include `csharp`, `bash`, `powershell`, `shell`, `sh`, `json`, `html`, `javascript`, `typescript`, `css`, `razor`, `xml`, `sql`, `sqlite`, `txt`, `diff`, and `mermaid`.
+* Prefer `csharp` over `cs` to set the language for C# code blocks.
 * Add a title to the code block. You can do this adding the title as a comment in the first line of the code block (e.g. `// Program.cs`).
 * Use [expressive code features](https://starlight.astro.build/guides/authoring-content/#expressive-code-features).
 * Readers should not need to scroll horizontally to read a code example. Simplify and condense the code as much as possible.
@@ -155,7 +154,7 @@ WebStorm has Grazie as a built-in spell checker and grammar checker, and support
 * Mention NuGet packages as a `bash` code block showing how to install it (`dotnet add package ...`). Link to the NuGet Gallery.
 * When referencing a property, field, class, or other symbol in text, use the `test` format instead of _test_.
 * Values should also be back-ticked, especially HTTP Status codes like `404` or `401`.
-* Make sure code blocks start at the very first character space and don't have excessive starting padding.
+* Avoid excessive indentation in code blocks; use column 0 unless indentation is needed to nest under lists or MDX components.
 
 ### Frontmatter Rules