Configure duplicate headers markdown rule and address violations (#5782)

.markdownlint.json

@@ -1,7 +1,9 @@
 {
     "default": true,
     "MD013": false, // line length
-    "MD024": false, // no-duplicate-heading Multiple headings with the same content
+    "MD024": { // no-duplicate-heading Multiple headings with the same content
+        "siblings_only": true
+    },
     "MD033": false, // no inline HTML
 
     // The following rules are disabled to allow the linter to be enabled.

documentation/vulnerability-reporting.md

@@ -71,6 +71,8 @@ $myImage="<insert-my-image-tag>"
 &([scriptblock]::Create((Invoke-WebRequest -UseBasicParsing 'https://raw.githubusercontent.com/dotnet/dotnet-docker/main/documentation/scripts/resolve-image-digest.ps1'))) $myImage
 ```
 
+#### Resolving multi-arch tags
+
 If the script above returns an error indicating it's unable to resolve a multi-arch tag, you'll need to provide extra parameters to the script.
 The following scripts indicate how to do that.
 
@@ -81,7 +83,7 @@ You only need the first three parts of the version number.
 In the case of Windows Server 2022, it's `10.0.20348`.
 You can use a wildcard to indicate the rest of the version number.
 
-#### macOS/Linux
+##### macOS/Linux
 
 Requires [PowerShell to be installed](https://learn.microsoft.com/powershell/scripting/install/installing-powershell-on-linux).
 
@@ -93,7 +95,7 @@ osVersion="<windows-version>" # Only used for Windows containers (e.g. "10.0.203
 curl -sSL https://raw.githubusercontent.com/dotnet/dotnet-docker/main/documentation/scripts/resolve-image-digest.ps1 | pwsh /dev/stdin $myImage -Os $os -Architecture $arch -OsVersion $osVersion
 ```
 
-#### Windows
+##### Windows
 
 ```powershell
 $myImage="<insert-my-image-tag>"

samples/run-in-sdk-container.md

@@ -53,13 +53,13 @@ You can test this working by simply editing [Program.cs](dotnetapp/Program.cs).
 
 The following instructions demonstrate this scenario in various environments.
 
-## Linux or macOS
+### Linux or macOS
 
 ```console
 docker run --rm -it -v $(pwd):/app/ -w /app mcr.microsoft.com/dotnet/sdk:8.0 dotnet run
 ```
 
-## Windows using Linux containers
+### Windows using Linux containers
 
 This example uses PowerShell.
 
@@ -67,7 +67,7 @@ This example uses PowerShell.
 docker run --rm -it -v ${pwd}:/app/ -w /app mcr.microsoft.com/dotnet/sdk:8.0 dotnet run
 ```
 
-## Windows using Windows containers
+### Windows using Windows containers
 
 This example uses PowerShell.
 
@@ -123,7 +123,7 @@ This example uses PowerShell.
 docker run --rm -it -p 8000:8080 -v ${pwd}:C:\app\ -w \app -e ASPNETCORE_HTTP_URLS=8080 -e ASPNETCORE_ENVIRONMENT=Development mcr.microsoft.com/dotnet/sdk:8.0 dotnet run --no-launch-profile
 ```
 
-### Using a launch profile to configure ASP.NET Core
+## Using a launch profile to configure ASP.NET Core
 
 The examples above use environment variables to configure ASP.NET Core. You can instead [configure ASP.NET Core with a launchSettings.json file](https://docs.microsoft.com/aspnet/core/fundamentals/environments). The [launchSettings.json file](aspnetapp/aspnetapp/Properties/launchSettings.json) in this app has been updated with a `container` profile that can be used instead of specifying environment variables with the docker CLI.