Workaround invalid link

.github/linters/.markdown-lint.yml

@@ -2,4 +2,5 @@ default: true
 MD013: # line length
   code_block_line_length: 256
   heading_line_length: 96
+  line_length: 96
 MD033: false # no inline HTML

Documentation/sourcebuild-in-repos/build-info.md

@@ -3,7 +3,7 @@
 This is a collection of notes about how source-build can differ in general from
 your repo's build and what kind of issues that can create.
 
-## Single version and single RID build
+## Single-version and single-RID build
 
 Source-build is required to build on a single machine with no internet access.
 This means that we build targeting a single RID, usually the non-portable RID

Documentation/sourcebuild-in-repos/update-dependencies.md

@@ -41,8 +41,8 @@ what can happen is
 1. In version 2, Package A is split into Package A1 and Package A2.
 1. A downstream repo is never updated to take the split packages.
 1. The version 2 source-build succeeds because Package A exists in the
-  [previously-source-built archive](build-info.md#single-version-and-single-rid-build), but no new
-  version of Package A is produced.
+  [previously-source-built archive](build-info.md#single-version-and-single-rid-build),
+  but no new version of Package A is produced.
 1. Source-build version 3 fails because Package A no longer exists in the
   previously-source-built archive either.
 

README.md

@@ -1,7 +1,5 @@
 # .NET Source-Build
 
-Test
-
 Please use [GitHub
 discussions](https://github.com/dotnet/source-build/discussions) to see
 announcements, ask questions, make suggestions, and share information with other