Fix dead links to the GitHub spec.

docs/faq.md

@@ -5,7 +5,7 @@ page_toc: false
 ---
 # FAQ
 <!-- #content -->
-These are some frequently asked questions about the [reference implementation](github.md) 
+These are some frequently asked questions about the [reference implementation](github/index.md) 
 of the [standard manifest format](spec.md) available in the 
 [SponsorLink](https://github.com/devlooped/SponsorLink/) and 
 [`gh-sponsors`](https://github.com/devlooped/gh-sponsors/) repositories.

docs/index.md

@@ -42,7 +42,7 @@ The synchronization is performed by a separate tool, which runs interactively so
 as to properly inform the user of the actions being taken and to ensure proper consent 
 is given before any data is exchanged.
 
-<!-- include github.md#sync -->
+<!-- include github/index.md#sync -->
 <!-- #sync -->
 ## Sponsor Manifest Sync
 
@@ -83,7 +83,7 @@ Whenever run, the tool performs the following steps:
 This implementation honors the recommended convention for manifest location and places them 
 at `~/.sponsorlink/github/[sponsorable].jwt`.
 <!-- #sync -->
-<!-- github.md#sync -->
+<!-- github/index.md#sync -->
 
 After a successful sync of the [sponsor manifest](spec.html#sponsor-manifest), the 
 libraries and tools can now check for its presence, authenticity and expiration 
@@ -92,5 +92,5 @@ libraries and tools can now check for its presence, authenticity and expiration
 *SponsorLink* itself does not dictate how a specific library or tool integrates 
 these checks, it only provides the [standard manifest format](spec.md) 
 that a sponsorable account backend needs to provide for local persistence 
-and subsequent (purely offline) checks. See [sponsoring checks](github.md#sponsoring-checks) 
+and subsequent (purely offline) checks. See [sponsoring checks](github/index.md#sponsoring-checks) 
 for some examples of how this might be done.

docs/spec/2.0.0-rc.1.md

@@ -148,7 +148,7 @@ The author may also choose to verify the token's expiration date, decide on a gr
 issue a notification if the manifest is expired.
 
 {: .note }
-> See the [GitHub implementation](github.md) of SponsorLink for more information.
+> See the [GitHub implementation](../github/index.md) of SponsorLink for more information.
 
 ## Privacy Considerations
 

docs/spec/2.0.0-rc.2.md

@@ -151,7 +151,7 @@ The author may also choose to verify the token's expiration date, decide on a gr
 issue a notification if the manifest is expired.
 
 {: .note }
-> See the [GitHub implementation](github.md) of SponsorLink for more information.
+> See the [GitHub implementation](../github/index.md) of SponsorLink for more information.
 
 ## Privacy Considerations
 

docs/spec/2.0.0.md

@@ -151,7 +151,7 @@ The author may also choose to verify the token's expiration date, decide on a gr
 issue a notification if the manifest is expired.
 
 {: .note }
-> See the [GitHub implementation](github.md) of SponsorLink for more information.
+> See the [GitHub implementation](../github/index.md) of SponsorLink for more information.
 
 ## Privacy Considerations
 

src/Cli/readme.md

@@ -53,5 +53,5 @@ Active SponsorLink sync usage by sponsorship kind:
 ![Team](https://img.shields.io/endpoint?color=8A2BE2&url=https%3A%2F%2Fsponsorlink.devlooped.com%2Fbadge%3Fteam)
 ![Contributor](https://img.shields.io/endpoint?color=blue&url=https%3A%2F%2Fsponsorlink.devlooped.com%2Fbadge%3Fcontrib)
 
-Learn more [about the tool](https://github.com/devlooped/SponsorLink/blob/main/docs/github.md#sponsor-manifest-sync) 
-and related [telemetry](https://github.com/devlooped/SponsorLink/blob/main/docs/github.md#telemetry).
+Learn more [about the tool](https://github.com/devlooped/SponsorLink/blob/main/docs/github/index.md#sponsor-manifest-sync) 
+and related [telemetry](https://github.com/devlooped/SponsorLink/blob/main/docs/github/index.md#telemetry).