template-update updated with reviewer comments

Author: “Emily

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

@@ -8,7 +8,7 @@ ifdef::context[:parent-context: {context}]
 
 
 ////
-Indicates that this file is an assembly:
+Metadata attribute that will help enable correct parsing and conversion to the appropriate DITA element.
 ////
 :_mod-docs-content-type: ASSEMBLY
 
@@ -20,7 +20,6 @@ Indicates that this file is an assembly:
 
 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}"]
 = My user story
 
@@ -64,7 +63,7 @@ include::modules/TEMPLATE_PROCEDURE_reference-material.adoc[leveloffset=+2]
 == Next steps
 
 * This section is optional.
-* Provide information about the next steps the user might want to take. T
+* Provide information about the next steps the user might want to take.
 * This section can include text and links. 
 
 // If the last module included in your assembly contains an Additional resources section as well, check the appearance of the rendered assembly. If the two Additional resources sections might be confusing for a reader, consider consolidating their content and removing one of them.

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

@@ -1,5 +1,5 @@
 ////
-Indicates the module type:
+Metadata attribute that will help enable correct parsing and conversion to the appropriate DITA element.
 ////
 
 :_mod-docs-content-type: CONCEPT
@@ -16,10 +16,9 @@ The `context` attribute enables module reuse. Every module ID includes {context}
 ////
 
 [id="my-concept-module-a_{context}"]
-
 = My concept module A
 ////
-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 or gerund. See also _Wording of headings_ in _The IBM Style Guide_.
+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 or gerund. See also _Wording of headings_ in _IBM Style_.
 
 Be sure to include a line break between the title and the module introduction.
 ////
@@ -34,8 +33,8 @@ The contents of a concept module give the user descriptions and explanations nee
 
 
 ////
-Do not include level three headings (===).
-Include titles and alternative text descriptions for images and enclose the descriptions in quotation marks (""). Alternative text should provide a textual, complete description of the image as a full sentence.
+Do not include third-level headings (===).
+Include titles and alternative text descriptions for images and enclose the descriptions in straight quotation marks (""). Alternative text should provide a textual, complete description of the image as a full sentence.
 Images should never be the sole means of conveying information and should only supplement the text.
 Avoid screenshots or other images that might quickly go out of date and that create a maintenance burden on documentation. Provide text equivalents for every diagram, image, or other non-text element. Avoid using images of text instead of actual text.
 ////

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

@@ -1,6 +1,6 @@
 
 ////
-Indicates the module type:
+Metadata attribute that will help enable correct parsing and conversion to the appropriate DITA element.
 ////
 
 :_mod-docs-content-type: PROCEDURE
@@ -17,7 +17,6 @@ The `context` attribute enables module reuse. Every module ID includes {context}
 ////
 
 [id="doing-procedure-a_{context}"]
-
 = Doing procedure A
 ////
 Start the title of a procedure module with a gerund, such as Creating, Installing, or Deploying.
@@ -38,7 +37,7 @@ Write a short introductory paragraph that provides an overview of the module. Th
 .. Do this other thing, and this other thing, and then select *Next*.
 . Use an unnumbered bullet (*) if the procedure includes only one step.
 +
-NOTE: You can add text, tables, code examples, images, and other items to a step. However, these items must be connected to the step the a plus sign (+). Any items under the .Procedure heading and before one of the following approved headings that are not connected to the last step with a plus sign cannot be converted to DITA.
+NOTE: You can add text, tables, code examples, images, and other items to a step. However, these items must be connected to the step with a plus sign (+). Any items under the .Procedure heading and before one of the following approved headings that are not connected to the last step with a plus sign cannot be converted to DITA.
 
 ////
 Only the following block headings can be reliably mapped to DITA: Prerequisites, Procedure, Verification, Troubleshooting, Troubleshooting steps, Next steps, Next step, Additional resources. They must appear in this order and, with the exception of Additional resources, are only allowed in a procedure module. You can also use block headings in figure, table, and example titles.

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

@@ -1,5 +1,5 @@
 ////
-Indicates the module type:
+Metadata attribute that will help enable correct parsing and conversion to the appropriate DITA element.
 ////
 :_mod-docs-content-type: REFERENCE
 
@@ -15,7 +15,6 @@ The `context` attribute enables module reuse. Every module ID includes {context}
 ////
 
 [id="reference-material_{context}"]
-
 = 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.