diff --git a/content/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps.md b/content/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps.md
index aa1fdac706..447fb90a2d 100644
--- a/content/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps.md
+++ b/content/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps.md
@@ -49,5 +49,5 @@ However, the activity ExampleApp is able to perform on Alice's behalf in {% data
 This means that, in order for ExampleApp to create an issue on Alice's behalf, in a repository called Repo A, all of the following must be true:
 
 * ExampleApp's {% data variables.product.prodname_github_app %} requests write access to issues.
-* A user having admin access for Repo A must have installed ExampleApp's {% data variables.product.prodname_github_app %} on Repo<code>&nbsp;</code>A.
+* A user having admin access for Repo A must have installed ExampleApp's {% data variables.product.prodname_github_app %} on Repo A.
 * Alice must have read permission for Repo A. For information about which permissions are required to perform various activities, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level)."