docs: typos

Author: cfoust

docs/src/architecture.md

@@ -80,7 +80,7 @@ This is useful because you can represent lots of things as a `Stream`:
 
 Streams can be composed and form pipes of arbitrary complexity. For example, `cy` records terminal sessions by proxying a `Stream` (sort of like `tee`.)
 
-However, for a terminal multiplexer this is clearly not enough. A `Stream` is stateless. In other words, there is no way to know what the state of the terminal that is attached to that `Stream`. That's where `Screen`s come in.
+However, for a terminal multiplexer this is clearly not enough. A `Stream` is stateless. In other words, there is no way to know the state of the terminal that is attached to that `Stream`. That's where `Screen`s come in.
 
 ### Screen
 
@@ -142,7 +142,7 @@ The flow for client input works like this:
 
 The flow for client output is somewhat simpler:
 
-1. Whenever the `Screen` the `Client` is attached to changes in some way (in other words, it produces an event that is published to its subscribers via `Subscribe`).
+1. The `Screen` the `Client` is attached to changes in some way (in other words, it produces an event that is published to its subscribers via `Subscribe`).
 2. The client's [`Renderer`](https://github.com/cfoust/cy/blob/main/pkg/mux/stream/renderer/module.go?plain=1#L24) receives this event and calls `State()` on the client's `Screen`, which produces a `tty.State`. The `Renderer` then calculates the sequence of bytes necessary to transform the actual client's terminal screen to match the `cy` server's state.
 3. This byte string is sent via the aforementioned WebSocket connection.
 4. It is ultimately `Read` by the user's terminal and written to standard output, thus triggering the visual changes the user expects.

docs/src/command-history.md

@@ -52,7 +52,7 @@ You must explicitly configure your shell (or any other program) to emit OSC-7 se
 
 ## How does it work?
 
-A terminal multiplexer is like a proxy: it is an intermediary between your actual terminal and one or more virtual terminals that it controls. It also responsible for passing the output a program (such as a shell) produces to its corresponding terminal. This control means that your terminal multiplexer can do whatever calculations it wants on that output, including (in `cy`'s case) recording it.
+A terminal multiplexer is like a proxy: it is an intermediary between your actual terminal and one or more virtual terminals that it controls. It is also responsible for passing the output that a program (such as a shell) produces to its corresponding terminal. This control means that your terminal multiplexer can do whatever calculations it wants on that output, including (in `cy`'s case) recording it.
 
 `cy` uses this ability to observe the state of the terminal before and after interpreting the output of the underlying process (otherwise known as a write made to standard output or error).
 

docs/src/groups-and-panes.md

@@ -8,7 +8,7 @@ A **pane** refers to a terminal window with a process running inside it, typical
 
 ## Groups
 
-Every pane `cy` belongs to a **group**. A group has a name and children, which consist of either panes or other groups.
+Every pane in `cy` belongs to a **group**. A group has a name and children, which consist of either panes or other groups.
 
 Groups also have two unique features:
 

docs/src/quick-start/the-layout.md

@@ -14,7 +14,7 @@ The layout shown above has a single pane that has its horizontal size fixed to 8
 
 {{story cast quick-start/layout --width 120 --height 26}}
 
-`cy`'s has pane and split functionality that should feel familiar to users of tmux. Like other terminal multiplexers, in `cy` you can divide your screen up into any number of panes. This can be done with {{bind :root ctrl+a -}} to split the current pane along a horizontal line and {{bind :root ctrl+a |}} to split along a vertical one.
+`cy` has pane and split functionality that should feel familiar to users of tmux. Like other terminal multiplexers, in `cy` you can divide your screen up into any number of panes. This can be done with {{bind :root ctrl+a -}} to split the current pane along a horizontal line and {{bind :root ctrl+a |}} to split along a vertical one.
 
 After creating a few, you can move between them using directional keys:
 

docs/src/replay-mode/modes.md

@@ -42,7 +42,7 @@ Copy mode also allows you to swap between the terminal's main and alt screens us
 
 #### Visual mode
 
-Visual mode is initiated when you press {{bind :copy v}} (by default). It works almost exactly like `vim`'s visual mode does; after you have some selected some text, you can yank it into your buffer with {{bind :copy y}} and paste it elsewhere with {{bind :root ctrl+a P}}.
+Visual mode is initiated when you press {{bind :copy v}} (by default). It works almost exactly like `vim`'s visual mode does; after you have selected some text, you can yank it into your buffer with {{bind :copy y}} and paste it elsewhere with {{bind :root ctrl+a P}}.
 
 #### Registers
 

pkg/cy/api/docs-cmd.md

@@ -20,7 +20,7 @@ Some examples:
 
 (cmd/path target)
 
-Get the working directory of the program running in the pane pane specified by `target`. `target` is a [NodeID](/api.md#nodeid).
+Get the working directory of the program running in the pane specified by `target`. `target` is a [NodeID](/api.md#nodeid).
 
 # doc: Title
 
@@ -42,7 +42,7 @@ Get the commands executed in a particular pane. Returns an array of [Commands](/
 
 # doc: Query
 
-Query all of the commands stored in the [commmand database](/command-history.md).
+Query all of the commands stored in the [command database](/command-history.md).
 
 # doc: Kill
 

pkg/cy/api/docs-input.md

@@ -11,11 +11,11 @@ This function supports a range of named parameters that adjust its functionality
 - `:animated` (boolean): Enable and disable background animation.
 - `:case-sensitive` (boolean): Whether the matching algorithm should respect differences in case. The default is `false`.
 - `:full` (boolean): If true, occupy the entire screen.
-- `:headers` ([]string): Provide a title for each column. This mostly used for filtering tabular data.
+- `:headers` ([]string): Provide a title for each column. This is mostly used for filtering tabular data.
 - `:prompt` (string): The text that will be shown beneath the search window.
 - `:reverse` (boolean): Display from the top of the screen (rather than the bottom.)
 - `:width` (int): Set the width of the match window (if not in full screen mode.)
-- `:height` (int): Set the maximum height of the match window. This applies bth in full screen and floating mode.
+- `:height` (int): Set the maximum height of the match window. This applies both in full screen and floating mode.
 
 # doc: Text
 

pkg/cy/api/docs-replay.md

@@ -76,7 +76,7 @@ Move cursor up one cell.
 
 Set the playback rate to `rate`. Positive numbers indicate a multiplier of real time moving _forwards_, negative numbers, _backwards_. For example, a rate of `2` means that time will advance at twice the normal speed; `-2` means that time will go backwards at -2x.
 
-`rate` is clamped to the range [10, 10].
+`rate` is clamped to the range [-10, 10].
 
 # doc: Copy
 
@@ -116,7 +116,7 @@ Jump to the cell before `char` after the cursor on the current line.
 
 (replay/jump-to-backward char)
 
-Jump to the cell before `char` after the cursor on the current line.
+Jump to the cell after `char` before the cursor on the current line.
 
 # doc: Open
 

pkg/cy/api/docs-tree.md

@@ -32,7 +32,7 @@ Get the path of `node`, which is a [NodeID](/api.md#nodeid).
 
 (tree/parent node)
 
-Get the [NodeID](/api.md#nodeid) for the parent of `node`. If `node` is `:root`, return `(tree/parent)` returns `nil`.
+Get the [NodeID](/api.md#nodeid) for the parent of `node`. If `node` is `:root`, `(tree/parent)` returns `nil`.
 
 # doc: Rm