Tweaked checklist and moved into base-checklist

base/base-checklist.md

@@ -1,15 +1,12 @@
 # {Doctype} checklist
-{
-Tip:
-
-* Before writing your {doctype} document, you should plan to address all items on the following checklist. Before finalizing, you should check they are complete.
-
-}
+This checklist list all items which should be addressed before completing a {doctype} document. It should be considered by an author while writing, and should used to guide reviewers.
 
+## Checklist
 * [ ] The document has been reviewed:
     * [ ] For clear writing and alignment with the writing style guide, ideally by a technical writer or editor.
-    * [ ] For alignment with the {doctype} template, ideally by a technical writer, information architect, or content strategist.
+    * [ ] For alignment with the [{doctype}-template](../{doctype}/{doctype}-template.md), ideally by a technical writer, information architect, or content strategist.
     * [ ] For technical accuracy, ideally by a technical subject matter expert.
-* [ ] {Further doctype specific checklist items ... .}
+* [ ] {Further doctype specific checklist items.}
 
-_TBD: See also: [the documentation maturity checklist](https://github.com/google/opendocs/blob/main/audit/checklist.md)_.
+## See also
+See also: [the documentation maturity checklist](https://github.com/google/opendocs/blob/main/audit/checklist.md).

base/base-theory.md

@@ -1,27 +1,12 @@
 # {Doctype} theory
 
-{Tip:
-
-* "Tips" should be removed from the final xxx-template-theory.
-}
-
 This {doctype}-theory document provides reasoning, justifications, and links to research relevant to {doctype} documentation. It aims to empower authors to "think like a tech writer and expert in {doctype} documents" and make decisions backed by best practices.
 
 **Version:** {MAJOR.MINOR.PATCH}
 
 **Last updated:** {Month DD, YYYY}
 
 
-## Checklist
-
-Before writing your {doctype} document, you should plan to address all items on the following checklist. Before finalizing, you should check they are complete.
-
-* [ ] The document has been reviewed:
-    * [ ] For clear writing and alignment with the writing style guide, ideally by a technical writer or editor.
-    * [ ] For alignment with the {doctype} template, ideally by a technical writer, information architect, or content strategist.
-    * [ ] For technical accuracy, ideally by a technical subject matter expert.
-* [ ] {Further doctype specific checklist items ... .}
-
 ## User stories
 
 When writing, it is important to understand who you are writing for, and ensure that you provide just the right amount of information to address their needs. The following user stories should help you achieve that.