diff --git a/website/developer-docs/docs/templates/procedural.md b/website/developer-docs/docs/templates/procedural.md
index a520022f4..53b3502cb 100644
--- a/website/developer-docs/docs/templates/procedural.md
+++ b/website/developer-docs/docs/templates/procedural.md
@@ -2,9 +2,9 @@
 title: "Procedural topic"
 ---
 
-Use a title that focuses on the task you are writing about... for example, "Add a new Group" or "Edit user profiles". For procedural docs, there should be a verb in the tilte, and usually the noun (the thing you are working on). For the title (and all headings) use the infinitive form of the verb (i.e. "add") not the gerund form (i.e. "adding").
+Use a title that focuses on the task you are writing about... for example, "Add a new Group" or "Edit user profiles". For procedural docs, there should be a verb in the title, and usually the noun (the component or object you are working on). For the title (and all headings) use the infinitive form of the verb (i.e. "add") not the gerund form (i.e. "adding").
 
-In this first section write one or two sentences about the task. Keep it brief; if it goes on too long, then create a separate conceptual topic, in a separate `.md` file. We don't want readers to have to scroll through paragraphs of conceptual info before they get to Step 1.
+In this first section, right after the title, write one or two sentences about the task. Keep it brief; if it goes on too long, then create a separate conceptual topic, in a separate `.md` file. We don't want readers to have to scroll through paragraphs of conceptual info before they get to Step 1.
 
 ## Prerequisites (optional section)
 
@@ -16,7 +16,7 @@ If the task is quite long or complex, it might be good to add a bullet list of t
 
 ## first several group steps
 
-If the task involves a lot of steps, try to group them into simalr steps and have a Head3 or Hedad4 title for each group.
+If the task involves a lot of steps, try to group them into similar steps and have a Head3 or Head4 title for each group.
 
 In this section, help the reader get oriented... where do they need to be (i.e. in the GUI, on a CLI, etc).
 
@@ -34,4 +34,4 @@ Use screenshots sparingly, only for complex UIs where it is difficult to describ
 
 ## verify the steps
 
-Whenever possible, it is useful to add verification steps at the end of a procedural topic. For example, if the procedural was about installing a product, use this section to tell them how they can verify that the install was successful
+Whenever possible, it is useful to add verification steps at the end of a procedural topic. For example, if the procedural was about installing a product, use this section to tell them how they can verify that the install was successful.