issues-109-111-115 removed references to Pantheon

Author: emmurphy1

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

@@ -1,8 +1,4 @@
 [id="introduction_{context}"]
 = Introduction to Modular Documentation
 
-This guide provides instructions on how to author modularly structured user stories. It defines terminology, describes components that form modular documentation, and provides instructions on how to use the provided modularization templates to create user stories. Most of the information included in this guide is generic. However, some instructions are required for documents that will be published on the Pantheon version 2 (V2) documentation management system. This requirement is noted where applicable.
-
-Pantheon V2 is an open-source modular documentation management system being developed by Red Hat. The engineering team is building the ability to import modular content written in AsciiDoc from one or more Git repositories, assign metadata to it to enhance search-engine optimization, and publish that content to one or more targets.
-
-The Pantheon community is still new but growing, and through ongoing development Red Hat aims to provide a solution that not only powers its own product documentation teams, but also offers greater flexibility to open source communities to create modular content that addresses individual use cases and can be drawn and combined from multiple sources.
+This manual provides instructions on how to author modularly structured documentation based on user stories. The manual defines used terminology, describes components that form modular documentation, and instructs writers on how to use provided templates to turn user stories into modular documentation.

modular-docs-manual/content/topics/module_anchor-and-file-names-concept.adoc

@@ -27,7 +27,7 @@ Create assembly and module file names that accurately and closely reflect the ti
 Do not include special characters in file names. Ensure that all members of your team use the same file naming conventions.
 ====
 
-These file naming guidelines are optional but highly recommended. However, if your team does not include the module prefixes in file names followed by either a hyphen (-) or an underscore (_), you must include one of the following variables in each concept, procedure, and reference module:
+These file naming guidelines are optional but highly recommended. However, if your team does not include the module prefixes in file names followed by either a hyphen (-) or an underscore (_), include one of the following variables in each concept, procedure, and reference module:
 
 [source]
 ----
@@ -36,8 +36,6 @@ These file naming guidelines are optional but highly recommended. However, if yo
 :system-module-type: REFERENCE
 ----
 
-NOTE: This is a requirement if you will publish on Pantheon V2. For more information, see xref:introduction_{context}[].
-
 .Anchors
 At the top of every module, provide an anchor in the format `+++[id="filename_{context}"]+++` where `filename` is the exact name of the file, without the file extension (`.adoc`). Module anchors are necessary so that Asciidoctor can identify the module when the module is reused or cross-referenced. The  `context` variable is defined in each assembly module, for example `:context: my-context-value`. When you build an assembly, the value of the `context` variable replaces `{context}` in each module anchor ID and appears in generated URL.