Link to @API Guardian GitHub repository

Author: sbrannen

documentation/src/docs/asciidoc/api-evolution.adoc

@@ -9,12 +9,13 @@ builders. That made changing JUnit 4 especially difficult and sometimes impossib
 That's why JUnit 5 introduces a defined lifecycle for all publicly available interfaces,
 classes, and methods.
 
-[[api-evolution-annotations]]
-=== API Annotations
+[[api-evolution-version-and-status]]
+=== API Version and Status
 
 Every published artifact has a version number `<major>.<minor>.<patch>`, and all publicly
-available interfaces, classes, and methods are annotated with {API}. The annotation's
-`status` attribute can be assigned one of the following values:
+available interfaces, classes, and methods are annotated with {API} from the
+{API_Guardian} project. The annotation's `status` attribute can be assigned one of the
+following values.
 
 [cols="20,80"]
 |===
@@ -39,8 +40,8 @@ value of lower stability.
 [[api-evolution-experimental-apis]]
 === Experimental APIs
 
-The following table lists which APIs are currently marked as _experimental_. Caution
-should be taken when relying on such APIs.
+The following table lists which APIs are currently designated as _experimental_ (via
+`@API(status = EXPERIMENTAL)`). Caution should be taken when relying on such APIs.
 
 |===
 | Package Name                               | Class Name                    | Type
@@ -80,8 +81,9 @@ should be taken when relying on such APIs.
 |===
 
 [[api-evolution-tooling]]
-=== Tooling Support
+=== @API Tooling Support
 
-The JUnit team plans to provide native tooling support for all JUnit users, extenders,
-and tool builders. The tooling support will likely provide a means to check if the JUnit
-APIs are being used in accordance with `@API` annotation declarations.
+The {API_Guardian} project plans to provide tooling support for publishers and consumers
+of APIs annotated with {API}. For example, the tooling support will likely provide a
+means to check if JUnit APIs are being used in accordance with `@API` annotation
+declarations.

documentation/src/docs/asciidoc/index.adoc

@@ -73,6 +73,7 @@ ifdef::backend-pdf[:imagesdir: {outdir}/{imagesdir}]
 :MockitoExtension:                  {junit5-samples-repo}/tree/{release-branch}/junit5-mockito-extension/src/main/java/com/example/mockito/MockitoExtension.java[MockitoExtension]
 //
 :API:                               https://apiguardian-team.github.io/apiguardian/docs/current/api/[@API]
+:API_Guardian:                      https://github.com/apiguardian-team/apiguardian[@API Guardian]
 :AssertJ:                           http://joel-costigliola.github.io/assertj/[AssertJ]
 :Gitter:                            https://gitter.im/junit-team/junit5[Gitter]
 :Hamcrest:                          http://hamcrest.org/JavaHamcrest/[Hamcrest]

documentation/src/docs/asciidoc/release-notes-5.0.0.adoc

@@ -21,7 +21,7 @@ on GitHub.
 ===== Deprecations and Breaking Changes
 
 * The `@API` annotation has been removed from the `junit-platform-commons` project and
-  relocated to a new standalone project on GitHub called the _@API Guardian_.
+  relocated to a new standalone project on GitHub called the {API_Guardian}.
 * Tags are no longer permitted to contain any of the following _reserved characters_.
   - `,`, `(`, `)`, `&`, `|`, `!`
 * The constructor for `FilePosition` has been replaced with a static factory method named