diff --git a/docs/tooling/cli/03-commands.md b/docs/tooling/cli/03-commands.md
index 5ce54e8b24..9d8dd1543e 100644
--- a/docs/tooling/cli/03-commands.md
+++ b/docs/tooling/cli/03-commands.md
@@ -253,7 +253,7 @@ Restores the changes made by the prepack command
 ## new
 
 The `new` command opens up an interactive guide for you to create new things
-in your app. If you do not pass in any options it is completely interactive, but in your app.
+in your app. If you do not pass in any options it is completely interactive, but
 it is possible to pre-select what you want to create using the `--select` flag,
 and provide options using `--option`, for example:
 
diff --git a/docs/tooling/cli/04-templates.md b/docs/tooling/cli/04-templates.md
index 5aa5fc30c4..2dd8f36daa 100644
--- a/docs/tooling/cli/04-templates.md
+++ b/docs/tooling/cli/04-templates.md
@@ -71,9 +71,9 @@ Custom templates can be installed from local directories. To install a template
 }
 ```
 
-Each entry in the `templates` array should be relative path that points to a directory containing a `portable-template.yaml` file. If the path starts with `./` it will be use as is, otherwise it will be resolved as a module within `node_modules`.
+Each entry in the `templates` array should be a relative path that points to a directory containing a `portable-template.yaml` file. If the path starts with `./` it will be use as is, otherwise it will be resolved as a module within `node_modules`.
 
-When defining the `templates` array it will override the default set of templates. If you want to keep using and of the build-in templates in the Backstage CLI you can reference them directly within the CLI package. This following is the full list of built-in templates:
+When defining the `templates` array it will override the default set of templates. If you want to keep using one of the build-in templates in the Backstage CLI you can reference them directly within the CLI package. This following is the full list of built-in templates:
 
 ```json
 {