From d8fff8267ab6ffe597cd2795f4a6a48ecc0c9fd4 Mon Sep 17 00:00:00 2001
From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
Date: Tue, 1 Feb 2022 10:11:39 -0800
Subject: [PATCH] Use reusable for GitHub name

---
 .../customizing-your-repository/about-code-owners.md            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
index 1afe82c79d..d6ac9ce97e 100644
--- a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
+++ b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
@@ -51,7 +51,7 @@ A CODEOWNERS file uses a pattern that follows most of the same rules used in [gi
 
 If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews.
 
-CODEOWNERS paths are case sensitive, because GitHub uses a case sensitive file system. Since CODEOWNERS are evaluated by GitHub, even systems (e.g. MacOS) that are case insensitive should ensure that paths and files are cased correctly in the CODEOWNERS file.
+CODEOWNERS paths are case sensitive, because {% data variables.product.prodname_dotcom %} uses a case sensitive file system. Since CODEOWNERS are evaluated by {% data variables.product.prodname_dotcom %}, even systems that are case insensitive (for example, macOS) must use paths and files that are cased correctly in the CODEOWNERS file.
 ### Example of a CODEOWNERS file
 ```
 # This is a comment.