issue-126 updated with dnaro comments

Author: emmurphy1

modular-docs-manual/content/topics/using_text_snippets_or_text_fragments.adoc

@@ -7,9 +7,9 @@
 // * ID: [id="my-concept-module-a_{context}"]
 // * Title: = My concept module A
 
-// The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
+// The ID is an anchor that links to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
 [id="using_text_snippets_or_text_fragments_{context}"]
-// The `context` attribute enables module reuse. Every module's ID includes a variable that sets the context, such as {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 a variable that sets the context, such as {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
 = Text Snippets or Text Fragments (Pseudo-modules)
 //In the title of concept modules, include nouns or noun phrases that are used in the body text. This helps readers and search engines find the information quickly.
 //Do not start the title of concept modules with a verb. See also _Wording of headings_ in _The IBM Style Guide_.

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

@@ -16,7 +16,7 @@ ifdef::context[:parent-context: {context}]
 * ID: [id="assembly-my-user-story_{context}"]
 * Title: = My user story
 
-The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken. Include {context} in the ID so the assembly can be reused.
+The ID is an anchor that links to the module. Avoid changing it after the module has been published to ensure existing links are not broken. Include {context} in the ID so the assembly can be reused.
 ////
 
 [id="assembly-my-user-story_{context}"]
@@ -28,7 +28,7 @@ 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's 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 even if it is reused multiple times in a guide.
 ////
 
 [role="_abstract"]

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

@@ -10,13 +10,13 @@ Base the file name and the ID on the module title. For example:
 ////
 
 ////
-The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
+The ID is an anchor that links to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
  ////
 
 [id="con-my-concept-module-a_{context}"]
 
 ////
-The `context` attribute enables module reuse. Every module's 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 even if it is reused multiple times in a guide.
 ////
 
 = My concept module A
@@ -25,7 +25,7 @@ In the title of concept modules, include nouns or noun phrases that are used in
 ////
 
 [role="_abstract"]
-A short introductory paragraph that provides an overview of the module is required.
+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.
 
 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

@@ -8,13 +8,13 @@ Base the file name and the ID on the module title. For example:
 * ID: [id="doing-procedure-a_{context}"]
 * Title: = Doing procedure A
 ////
- The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
+ The ID is an anchor that links to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
 ////
 
 [id="proc-doing-one-procedure_{context}"]
 
 ////
-The `context` attribute enables module reuse. Every module's 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 even if it is reused multiple times in a guide.
 ////
 
 = Doing one procedure
@@ -23,7 +23,7 @@ Start the title of a procedure module with a verb, such as Creating or Create. S
 ////
 
 [role="_abstract"]
-A short introductory paragraph that provides an overview of the module is required. Procedure modules should include both what users will do and why users want to do it.
+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.
 
 .Prerequisites
@@ -36,13 +36,15 @@ The `[role="_abstract"]` tag defines the first paragraph of the module for searc
 
 . Start each step with an active verb.
 
-. Include one command or action per step.
+. Include one command or action for each step with the exception of simple follow-step, for example:
+.. Do this thing and then select *Next*.
+.. Do this other thing and then select *Next*.
 
 . Use an unnumbered bullet (*) if the procedure includes only one step.
 
 .Verification steps
 ////
-Optional. Delete if not applicable. Provide the user with verification methods for the procedure, such as expected output or commands that can be used to check for success or failure.
+Delete this section if it does not apply to your module. Provide the user with verification methods for the procedure, such as expected output or commands that confirm success or failure.
 ////
 
 . Start each step with an active verb.

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

@@ -8,20 +8,20 @@ Base the file name and the ID on the module title. For example:
 * ID: [id="ref-my-reference-a_{context}"]
 * Title: = My reference A
 
-The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
+The ID is an anchor that links to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
 ////
 
 [id="ref-reference-material_{context}"]
 ////
-The `context` attribute enables module reuse. Every module's 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 even if it is reused multiple times in a guide
 ////
 = Reference material
 ////
 In the title of a reference module, include nouns that are used in the body text. For example, "Keyboard shortcuts for ___" or "Command options for ___." This helps readers and search engines find the information quickly.
 ////
 
 [role="_abstract"]
-A short introductory paragraph that provides an overview of the module is required.
+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.
 It has a very strict structure, often in the form of a list or a table.