From 993b1f6c52d6dc78826aa57c65f3475d45cd67f7 Mon Sep 17 00:00:00 2001
From: Octokrism <102750040+octokrism@users.noreply.github.com>
Date: Mon, 11 Apr 2022 00:37:06 +0930
Subject: [PATCH] Revert "Update authorizing-oauth-apps.md"

---
 .../apps/building-oauth-apps/authorizing-oauth-apps.md        | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
index fc1883a9d7fa..65161f18796c 100644
--- a/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
+++ b/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
@@ -302,10 +302,10 @@ subdirectory of the callback URL.
 
 The optional `redirect_uri` parameter can also be used for localhost URLs. If the application specifies a localhost URL and a port, then after authorizing the application users will be redirected to the provided URL and port. The `redirect_uri` does not need to match the port specified in the callback url for the app.
 
-For the `http://127.0.0.1/path` callback URL, you can use this `redirect_uri`:
+For the `http://localhost/path` callback URL, you can use this `redirect_uri`:
 
 ```
-http://127.0.0.1:1234/path
+http://localhost:1234/path
 ```
 
 ## Creating multiple tokens for OAuth Apps