From 02daba8744c8dc131a569d681acc57ab6e4ec06c Mon Sep 17 00:00:00 2001
From: Gitnitdun <104273036+Gitnitdun@users.noreply.github.com>
Date: Fri, 9 Sep 2022 13:11:50 -0500
Subject: [PATCH] Delete self-review.md

---
 contributing/self-review.md | 13 -------------
 1 file changed, 13 deletions(-)
 delete mode 100644 contributing/self-review.md

diff --git a/contributing/self-review.md b/contributing/self-review.md
deleted file mode 100644
index 7dc65b407ffc..000000000000
--- a/contributing/self-review.md
+++ /dev/null
@@ -1,13 +0,0 @@
-### Self review
-
-You should always review your own PR first.
-
-For content changes, make sure that you:
-
-- [ ] Confirm that the changes meet the user experience and goals outlined in the content design plan (if there is one).
-- [ ] Compare your pull request's source changes to staging to confirm that the output matches the source and that everything is rendering as expected. This helps spot issues like typos, content that doesn't follow the style guide, or content that isn't rendering due to versioning problems. Remember that lists and tables can be tricky.
-- [ ] Review the content for technical accuracy.
-- [ ] Review the entire pull request using the [localization checklist](localization-checklist.md).
-- [ ] Copy-edit the changes for grammar, spelling, and adherence to the [style guide](https://github.com/github/docs/blob/main/contributing/content-style-guide.md).
-- [ ] Check new or updated Liquid statements to confirm that versioning is correct.
-- [ ] If there are any failing checks in your PR, troubleshoot them until they're all passing.