Update the modular templates to match upstream changes:

* Clarify rules for text following [role="_abstract"] in the templates #160
* Inconsistent module IDs in the procedure module template #155

Author: msuchane

data/templates/assembly.adoc

@@ -34,7 +34,7 @@ The `context` attribute enables module reuse. Every module ID includes {context}
 
 [role="_abstract"]
 {% if examples -%}
-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.
+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.
 {%- endif %}
 
 == Prerequisites

data/templates/concept.adoc

@@ -27,7 +27,7 @@ In the title of concept modules, include nouns or noun phrases that are used in
 
 [role="_abstract"]
 {% if examples -%}
-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.
+Write a short introductory paragraph that provides an overview of the module.
 
 The contents of a concept module give the user descriptions and explanations needed to understand and use a product.
 

data/templates/procedure.adoc

@@ -1,7 +1,7 @@
 ////
 Base the file name and the ID on the module title. For example:
 * file name: proc-doing-procedure-a.adoc
-* ID: [id="doing-procedure-a_{context}"]
+* ID: [id="proc-doing-procedure-a_{context}"]
 * Title: = Doing procedure A
 
 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.
@@ -25,7 +25,9 @@ Start the title of a procedure module with a verb, such as Creating or Create. S
 
 [role="_abstract"]
 {% if examples -%}
-Write a short 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.
+Write a short introductory paragraph that provides an overview of the module.
+
+Procedure modules should include the steps that users perform and address user motivation.
 {%- endif %}
 
 .Prerequisites

data/templates/reference.adoc

@@ -25,8 +25,9 @@ In the title of a reference module, include nouns that are used in the body text
 
 [role="_abstract"]
 {% if examples -%}
-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. 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.
+Write a short introductory paragraph that provides an overview of the module.
+
+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: