diff --git a/docs/features/software-templates/writing-custom-actions.md b/docs/features/software-templates/writing-custom-actions.md
index 93ea23cdbd..480e0dbb14 100644
--- a/docs/features/software-templates/writing-custom-actions.md
+++ b/docs/features/software-templates/writing-custom-actions.md
@@ -109,14 +109,14 @@ export const createNewFileAction = () => {
 
 #### A note on naming conventions
 
-Try to keep names consistent for both your own custom actions, and any actions contributed to open source. We've found that a seperation of `:` and using a verb as the last part of the name works well.
+Try to keep names consistent for both your own custom actions, and any actions contributed to open source. We've found that a separation of `:` and using a verb as the last part of the name works well.
 We follow `provider:entity:verb` or as close to this as possible for our built in actions. For example, `github:actions:create` or `github:repo:create`.
 
 Also feel free to use your company name to namespace them if you prefer too, for example `acme:file:create`.
 
 Prefer to use `camelCase` over `pascalCase` for these actions if possible, which leads to better reading and writing of template entity definitions.
 
-> We're aware that theres some exceptions to this, but try to follow as close as possible. We'll be working on migrating these in the repository over time too.
+> We're aware that there are some exceptions to this, but try to follow as close as possible. We'll be working on migrating these in the repository over time too.
 
 ### The context object