diff --git a/.github/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
similarity index 100%
rename from .github/CODE_OF_CONDUCT.md
rename to CODE_OF_CONDUCT.md
diff --git a/.github/CONTRIBUTING.md b/CONTRIBUTING.md
similarity index 98%
rename from .github/CONTRIBUTING.md
rename to CONTRIBUTING.md
index f3321bbb..6a37aa7f 100644
--- a/.github/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -72,7 +72,7 @@ Here are a few things you can do that will increase the likelihood of your pull
 - Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
 
 ## Releasing a new Primer CSS version
-See [RELEASING.md](./RELEASING.md) for our release process.
+See [RELEASING.md](RELEASING.md) for our release process.
 
 ## Resources
 
diff --git a/.github/DEVELOP.md b/DEVELOP.md
similarity index 100%
rename from .github/DEVELOP.md
rename to DEVELOP.md
diff --git a/README.md b/README.md
index f4b85284..fb5c4d28 100644
--- a/README.md
+++ b/README.md
@@ -51,10 +51,10 @@ You can import individual Primer modules directly from the `@primer/css` package
 ```
 
 ## Development
-See [DEVELOP.md](./.github/DEVELOP.md) for development docs.
+See [DEVELOP.md](DEVELOP.md) for development docs.
 
 ## Releasing (for GitHub staff)
-You can find docs about our release process in [RELEASING.md](./.github/RELEASING.md).
+You can find docs about our release process in [RELEASING.md](RELEASING.md).
 
 ## License
 
diff --git a/.github/RELEASING.md b/RELEASING.md
similarity index 100%
rename from .github/RELEASING.md
rename to RELEASING.md