From b8b119e30d81c11de1ade834ea50d741fcba849a Mon Sep 17 00:00:00 2001
From: Ben Ahmady <32935794+subatoi@users.noreply.github.com>
Date: Fri, 15 Dec 2023 17:37:11 +0000
Subject: [PATCH] Removes 'Schema enforcement' section (#47907)

---
 .../writing-for-github-docs/versioning-documentation.md       | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/content/contributing/writing-for-github-docs/versioning-documentation.md b/content/contributing/writing-for-github-docs/versioning-documentation.md
index 9835efe53c57..18093dfbb1f5 100644
--- a/content/contributing/writing-for-github-docs/versioning-documentation.md
+++ b/content/contributing/writing-for-github-docs/versioning-documentation.md
@@ -242,10 +242,6 @@ versions:
   feature: 'some-new-feature'
 ```
 
-### Schema enforcement
-
-The schema for validating the feature versioning lives in [`src/content-linter/lib/feature-versions-schema.js`](https://github.com/github/docs/blob/main/src/content-linter/lib/feature-versions-schema.js) and is exercised by [`tests/linting/lint-versioning.js`](https://github.com/github/docs/blob/main/src/content-linter/tests/lint-versioning.js).
-
 ## Best practices
 
 Versioned content impacts the reader, but also impacts anyone who contributes to or reviews the content. Here are a few tips to improve the writing, reading, and reviewing experience for versioning syntax. None of these practices are mandatory and you will find edge and corner cases, but they're intended as useful heuristics to help you think through versioning.