Fix a few more typos

CONTRIBUTING.md

@@ -54,4 +54,4 @@ We're happy to pair with you to help you learn the codebase and get your contrib
 Reviewing code in a pull request, after the fact, is hard and tedious - the team generally likes to build trust and review code through pair programming.
 We'd prefer have conversations about the code, through Zed, while it is being written, so decisions can be made in real-time and less time is spent on fixing things after the fact. Ideally, GitHub is only used to merge code that has already been discussed and reviewed in Zed.
 
-Remeber that smaller, incremental PRs are easier to review and merge than large PRs.
+Remember that smaller, incremental PRs are easier to review and merge than large PRs.

crates/collab/src/rpc.rs

@@ -3116,7 +3116,7 @@ async fn leave_channel_chat(request: proto::LeaveChannelChat, session: Session)
     Ok(())
 }
 
-/// Retrive the chat history for a channel
+/// Retrieve the chat history for a channel
 async fn get_channel_messages(
     request: proto::GetChannelMessages,
     response: Response<proto::GetChannelMessages>,

crates/gpui/src/app.rs

@@ -967,8 +967,8 @@ impl AppContext {
     }
 
     /// Register a callback to be invoked when a keystroke is received by the application
-    /// in any window. Note that this fires after all other action and event mechansims have resolved
-    /// and that this API will not be invoked if the event's propogation is stopped.
+    /// in any window. Note that this fires after all other action and event mechanisms have resolved
+    /// and that this API will not be invoked if the event's propagation is stopped.
     pub fn observe_keystrokes(
         &mut self,
         f: impl FnMut(&KeystrokeEvent, &mut WindowContext) + 'static,

crates/gpui/src/elements/list.rs

@@ -615,7 +615,7 @@ mod test {
         // Reset
         state.reset(5);
 
-        // And then recieve a scroll event _before_ the next paint
+        // And then receive a scroll event _before_ the next paint
         cx.simulate_event(ScrollWheelEvent {
             position: point(px(1.), px(1.)),
             delta: ScrollDelta::Pixels(point(px(0.), px(-500.))),

crates/gpui/src/view.rs

@@ -200,7 +200,7 @@ impl<V> PartialEq for WeakView<V> {
 
 impl<V> Eq for WeakView<V> {}
 
-/// A dynically-typed handle to a view, which can be downcast to a [View] for a specific type.
+/// A dynamically-typed handle to a view, which can be downcast to a [View] for a specific type.
 #[derive(Clone, Debug)]
 pub struct AnyView {
     model: AnyModel,

crates/vim/src/vim.rs

@@ -332,7 +332,7 @@ impl Vim {
         }
     }
 
-    /// Explicitly record one action (equiavlent to start_recording and stop_recording)
+    /// Explicitly record one action (equivalents to start_recording and stop_recording)
     pub fn record_current_action(&mut self, cx: &mut WindowContext) {
         self.start_recording(cx);
         self.stop_recording();

docs/old/release-process.md

@@ -90,7 +90,7 @@ This means that when releasing a new version of Zed that has changes to the RPC
 1. If needing a migration:
    - First check that the migration is valid. The database serves both preview and stable simultaneously, so new columns need to have defaults and old tables or columns can't be dropped.
    - Then use `script/deploy-migration` <release channel> <version number> (production, staging, preview, nightly). ex: `script/deploy-migration preview 0.19.0`
-    - If there is an 'Error: container is waiting to start', you can review logs manually with: `kubectl --namespace <enviroment> logs <pod name>` to make sure the mgiration ran successfully.
+    - If there is an 'Error: container is waiting to start', you can review logs manually with: `kubectl --namespace <environment> logs <pod name>` to make sure the mgiration ran successfully.
 1. Once that CI job completes, you will be able to run the following command to deploy that docker image. The script takes two arguments: an environment (`production`, `preview`, or `staging`), and a version number (e.g. `0.10.1`):
 
 ```