From 16ab321334726996510446878bde550540aeaa28 Mon Sep 17 00:00:00 2001
From: Katrin Leinweber <9948149+katrinleinweber@users.noreply.github.com>
Date: Thu, 18 Apr 2019 11:14:01 +0200
Subject: [PATCH] Swap @18F's archived README guide for @dguo's

---
 _articles/starting-a-project.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_articles/starting-a-project.md b/_articles/starting-a-project.md
index 1d7790b3fbc..af7dfccebcc 100644
--- a/_articles/starting-a-project.md
+++ b/_articles/starting-a-project.md
@@ -165,7 +165,7 @@ You can use your README to answer other questions, like how you handle contribut
 
 Sometimes, people avoid writing a README because they feel like the project is unfinished, or they don't want contributions. These are all very good reasons to write one.
 
-For more inspiration, try using @18F's ["Making READMEs Readable"](https://pages.18f.gov/open-source-guide/making-readmes-readable/) or @PurpleBooth's [README template](https://gist.github.com/PurpleBooth/109311bb0361f32d87a2) to write a complete README.
+For more inspiration, try using @dguo's ["Make a README" guide](https://www.makeareadme.com/) or @PurpleBooth's [README template](https://gist.github.com/PurpleBooth/109311bb0361f32d87a2) to write a complete README.
 
 When you include a README file in the root directory, GitHub will automatically display it on the repository homepage.