diff --git a/docs/src/contribute-to-zed.md b/docs/src/contribute-to-zed.md
index c58db20cef..54346813be 100644
--- a/docs/src/contribute-to-zed.md
+++ b/docs/src/contribute-to-zed.md
@@ -1,6 +1,6 @@
 # Contributing to Zed
 
-Thank you for your interest in contributing to the Zed! Before making contributions, we recommend reading our [CONTRIBUTRING.md](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md) guidelines. This document provides a detailed guide to contributing to Zed.
+Thank you for your interest in contributing to the Zed! Before making contributions, we recommend reading our [CONTRIBUTING.md](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md) guidelines. This document provides a detailed guide to contributing to Zed.
 
 ### Issues
 
diff --git a/docs/src/development/releases.md b/docs/src/development/releases.md
index ecf01fdc9e..8cf29911be 100644
--- a/docs/src/development/releases.md
+++ b/docs/src/development/releases.md
@@ -2,8 +2,8 @@
 
 Zed currently maintains two public releases for macOS:
 
-- [Stable](https://zed.dev/download). This is the primary version that people download and use.
-- [Preview](https://zed.dev/releases/preview), which receives updates a week ahead of stable for early adopters.
+- [Stable](https://zed.dev/download): This is the primary version that people download and use.
+- [Preview](https://zed.dev/releases/preview): which receives updates a week ahead of Stable for early adopters.
 
 Typically we cut a new minor release every Wednesday. The current Preview becomes Stable, and the new Preview contains everything on main up until that point.
 
@@ -24,7 +24,7 @@ You will need write access to the Zed repository to do this:
   - Copy the release notes from the previous Preview release(s) to the current Stable release.
   - Download the artifacts for each release and test that you can run them locally.
   - Publish the releases on GitHub.
-  - Tweet the tweets (Credentials are in 1password).
+  - Tweet the tweets (Credentials are in 1Password).
 
 ## Patch release process