From f89d77db60b18d8b4592a038d9c2b13d08faa9db Mon Sep 17 00:00:00 2001
From: Hamish Willee <hamishwillee@gmail.com>
Date: Sun, 7 Mar 2021 15:18:07 -0800
Subject: [PATCH] Fix self-link to page as per issue 2911 (#2913)

---
 files/en-us/web/http/cors/index.html | 2 --
 1 file changed, 2 deletions(-)

diff --git a/files/en-us/web/http/cors/index.html b/files/en-us/web/http/cors/index.html
index 09f4ae1f245bc8a..142e06a8f45a463 100644
--- a/files/en-us/web/http/cors/index.html
+++ b/files/en-us/web/http/cors/index.html
@@ -58,8 +58,6 @@ <h2 id="Examples_of_access_control_scenarios">Examples of access control scenari
 
 <p>We present three scenarios that demonstrate how Cross-Origin Resource Sharing works. All these examples use {{domxref("XMLHttpRequest")}}, which can make cross-site requests in any supporting browser.</p>
 
-<p>A discussion of Cross-Origin Resource Sharing from a server perspective (including PHP code snippets) can be found in the <a class="internal" href="/en-US/docs/Web/HTTP/CORS">Server-Side Access Control (CORS)</a> article.</p>
-
 <h3 id="Simple_requests">Simple requests</h3>
 
 <p>Some requests don’t trigger a <a href="#preflighted_requests">CORS preflight</a>. Those are called <em>“simple requests”</em> in this article, though the {{SpecName('Fetch')}} spec (which defines CORS) doesn’t use that term. A “simple request” is one that <strong>meets all the following conditions</strong>:</p>