issue-126 updated with oraNod comments

Author: emmurphy1

modular-docs-manual/files/TEMPLATE_ASSEMBLY_a-collection-of-modules.adoc

@@ -28,11 +28,11 @@ If the assembly covers a task, start the title with a verb in the gerund form, s
 :context: assembly-keyword
 
 ////
-The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
+The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID so you can include it multiple times in the same guide.
 ////
 
 [role="_abstract"]
-This paragraph is the assembly introduction. It explains what the user will accomplish by working through the modules in the assembly and sets the context for the user story the assembly is based on. The `[role="_abstract"]` tag defines the first paragraph of the introduction for search metadata.
+This paragraph is the assembly introduction. It explains what the user will accomplish by working through the modules in the assembly and sets the context for the user story the assembly is based on. The text that immediately follows the `[role="_abstract"]` tag is used for search metadata.
 
 .Prerequisites
 

modular-docs-manual/files/TEMPLATE_CONCEPT_concept-explanation.adoc

@@ -16,7 +16,7 @@ The ID is an anchor that links to the module. Avoid changing it after the module
 [id="con-my-concept-module-a_{context}"]
 
 ////
-The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
+The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID so you can include it multiple times in the same guide.
 ////
 
 = My concept module A
@@ -25,8 +25,7 @@ In the title of concept modules, include nouns or noun phrases that are used in
 ////
 
 [role="_abstract"]
-Provide a short introductory paragraph that gives an overview of the module.
-It provides an overview of the module. The `[role="_abstract"]` tag defines the first paragraph of the module for search metadata.
+Write a short introductory paragraph that provides an overview of the module. The text that immediately follows the `[role="_abstract"]` tag is used for search metadata.
 
 The contents of a concept module give the user descriptions and explanations needed to understand and use a product.
 

modular-docs-manual/files/TEMPLATE_PROCEDURE_doing-one-procedure.adoc

@@ -14,7 +14,7 @@ Base the file name and the ID on the module title. For example:
 [id="proc-doing-one-procedure_{context}"]
 
 ////
-The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
+The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID so you can include it multiple times in the same guide.
 ////
 
 = Doing one procedure
@@ -23,8 +23,7 @@ Start the title of a procedure module with a verb, such as Creating or Create. S
 ////
 
 [role="_abstract"]
-Provide a short introductory paragraph that gives an overview of the module. Procedure modules should include  the steps that users perform and address user motivation.
-The `[role="_abstract"]` tag defines the first paragraph of the module for search metadata.
+Write a introductory paragraph that provides an overview of the module. Procedure modules should include the steps that users perform and address user motivation. The text that immediately follows the `[role="_abstract"]` tag is used for search metadata.
 
 .Prerequisites
 
@@ -49,9 +48,11 @@ Delete this section if it does not apply to your module. Provide the user with v
 
 . Start each step with an active verb.
 
-. Include one command or action per step.
+. Include one non-trivial command or action for each step:
+.. Do this thing and then click *Next*.
+.. Do this other thing.
 
-. Use an unnumbered bullet (*) if the procedure includes only one step.
+. Use an unordered list item (*) if the procedure includes only one step.
 
 
 [role="_additional-resources"]

modular-docs-manual/files/TEMPLATE_REFERENCE_reference-material.adoc

@@ -13,7 +13,7 @@ The ID is an anchor that links to the module. Avoid changing it after the module
 
 [id="ref-reference-material_{context}"]
 ////
-The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide
+The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID so you can include it multiple times in the same guide.
 ////
 = Reference material
 ////
@@ -22,8 +22,7 @@ In the title of a reference module, include nouns that are used in the body text
 
 [role="_abstract"]
 Provide a short introductory paragraph that gives an overview of the module.
-The `[role="_abstract"]` tag defines the first paragraph of the module for search metadata.
-A reference module provides data that users might want to look up, but do not need to remember.
+The `[role="_abstract"]` tag defines the first paragraph of the module for search metadata. A reference module provides data that users might want to look up, but do not need to remember.
 It has a very strict structure, often in the form of a list or a table.
 A well-organized reference module enables users to scan it quickly to find the details they want.
 AsciiDoc markup to consider for reference data: