From 5871a53acca7dcee72d1a96eeaf4bf277d1a78a6 Mon Sep 17 00:00:00 2001
From: Matt <85322+mattmassicotte@users.noreply.github.com>
Date: Mon, 16 Dec 2024 15:17:40 -0500
Subject: [PATCH] Factor out link

---
 Edit/Chime.docc/AddLanguage.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/Edit/Chime.docc/AddLanguage.md b/Edit/Chime.docc/AddLanguage.md
index 0b00108..f5c1012 100644
--- a/Edit/Chime.docc/AddLanguage.md
+++ b/Edit/Chime.docc/AddLanguage.md
@@ -14,7 +14,7 @@ Chime relies heavily internally on [UTIs](https://developer.apple.com/documentat
 mdls path/to/your/file
 ```
 
-These UTIs should first be incorporated into [ChimeKit](https://github.com/ChimeHQ/ChimeKit). From there, they can be added as "Imported Type Identifiers" in Chime's Info.plist. To do this, you'll need to know the file extensions used. ChimeKit also supports well-known file names, like `Makefile`, which the Uniform Type Identifier APIs do not currently support. 
+These UTIs should first be incorporated into [ChimeKit][]. From there, they can be added as "Imported Type Identifiers" in Chime's Info.plist. To do this, you'll need to know the file extensions used. ChimeKit also supports well-known file names, like `Makefile`, which the Uniform Type Identifier APIs do not currently support. 
 
 ## Tree-Sitter
 
@@ -40,4 +40,6 @@ You might also be tempted to adjust these queries. Try to resist this temptation
 
 ## Language Server
 
-After syntactic support is working, you can refer to ChimeKit's documentation on how to set up an extension for language server support.
+After syntactic support is working, you can refer to [ChimeKit]'s documentation on how to set up an extension for language server support.
+
+[ChimeKit]: https://github.com/ChimeHQ/ChimeKit