diff --git a/contributions/hack-day.md b/contributions/hack-day.md
index 0a04df3a..bf27d1a9 100644
--- a/contributions/hack-day.md
+++ b/contributions/hack-day.md
@@ -4,7 +4,7 @@ Welcome to [WP-CLI Hack Day](https://make.wordpress.org/cli/2024/04/02/save-the-
 
 **We'd love to help you submit at least one pull request today**. Given this goal, you'll likely want to **start with something small and attainable**. After you've submitted your first pull request for the day, you're welcome to work on something more ambitious.
 
-When do you submit a pull request during Hack Day, please add <code>Related https://github.com/wp-cli/wp-cli/issues/5935</code> so we can easily keep track of them. We'll include them in a recap post at the end of the day.
+When you submit a pull request during Hack Day, please add <code>Related https://github.com/wp-cli/wp-cli/issues/5935</code> so we can easily keep track of them. We'll include them in a recap post at the end of the day.
 
 We put together this guide to make contributing as straightforward as possible. Please also join the [#cli channel in WordPress.org Slack](https://wordpress.slack.com/messages/C02RP4T41) ([sign up instructions](https://make.wordpress.org/chat/)) to chat with other contributors, for questions, etc.
 
diff --git a/guides/running-commands-remotely.md b/guides/running-commands-remotely.md
index c9b1a348..da64353a 100644
--- a/guides/running-commands-remotely.md
+++ b/guides/running-commands-remotely.md
@@ -193,7 +193,7 @@ The solution: On the remote configure `~/.bashrc` like this:
   - `alias wp="php ~/bin/wp"`
   - or
   - `alias wp="php ~/bin/wp-cli.phar"`
-- In other words: You have an alias "wp" which is a one liner where php runs the WP-CLI binary by stating the path to the `wpi-cli.phar` file, wherever it may be, under whatever name it may have.
+- In other words: You have an alias "wp" which is a one liner where php runs the WP-CLI binary by stating the path to the `wp-cli.phar` file, wherever it may be, under whatever name it may have.
   - `php` is allowed on basically any webhost.
   - And the `wp-cli.phar` file itself must not even have the execute flag set (="can be entirely passive"), as formally the file gets run (=interpreted) by `php`. **Note:** An executable `~/bin/wp` file (the renamed `wp-cli.phar` with an execute flag) of course also gets run by the `php` interpreter eventually. But the invocation in the shell is formally different. And that is what makes the crucial difference here.