docs(concept): simplify "Required facts" headings to concept names

Remove redundant "Required facts about" prefix from headings since
they're already under a "## Facts" section.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: jgeluk

docs/concept/concept/concept-vocabulary.md

@@ -404,7 +404,7 @@ domain, enabling reuse and consistency across use cases_
     - Clear traceability of which terms are considered equivalent in
       which contexts
 
-    ### Required facts
+    ### Concept Vocabulary
 
     - **Identifier**
         - A Concept Vocabulary must have an **opaque**, **universally

docs/concept/concept/index.md

@@ -249,7 +249,7 @@ reason about business concepts_
         minimal facts you can use to build your own ontology, schema,
         or graph model.
 
-    ### Required facts about a Concept
+    ### Concept
 
     - **Opaque universally unique identifier**
         - A Concept must have an **opaque**, **universally unique** identifier.

docs/concept/concept/story-concept-relationship.md

@@ -59,7 +59,7 @@ or dependent)_
         minimal facts you can use to build your own ontology, schema,
         or graph model.
 
-    ### Required facts about a Story/Concept Relationship
+    ### Story/Concept Relationship
     - **Opaque universally unique identifier**: A UUID representing this specific relationship instance.
     - **Source Story**: A reference to the [Story](../story.md) that owns this relationship.
     - **Target Concept**: A reference to the [Concept](index.md) being used.

docs/concept/outcome/index.md

@@ -212,7 +212,7 @@ requirement_
         minimal facts you can use to build your own ontology, schema,
         or graph model.
 
-    ### Required facts about an Outcome
+    ### Outcome
 
     - **Opaque universally unique identifier**
         - An Outcome should have an **opaque**, **universally unique**

docs/concept/outcome/outcome-relationship.md

@@ -65,7 +65,7 @@ contribution mapping_
         minimal facts you can use to build your own ontology, schema,
         or graph model.
 
-    ### Required facts about an Outcome Relationship
+    ### Outcome Relationship
     - **Opaque universally unique identifier**: A UUID representing
       this relationship instance.
     - **Source Use Case**: A reference to the [Use

docs/concept/outcome/outcome-stereotype.md

@@ -425,7 +425,7 @@ Goals, Objectives, KPIs, and Success Criteria_
 
     An Outcome Stereotype is a classification applied to an Outcome:
 
-    ### Required facts
+    ### Outcome Stereotype
 
     - **Outcome** must reference zero or one **Outcome Stereotype**
     - **Outcome Stereotype** has a **name** (e.g., "Goal",

docs/concept/persona/index.md

@@ -230,7 +230,7 @@ or entities — involved in a Use Case, defined using business language_
         minimal facts you can use to build your own ontology, schema,
         or graph model.
 
-    ### Required facts about a Persona
+    ### Persona
 
     - **Opaque universally unique identifier**
         - A Persona should have an **opaque**, **universally unique** identifier.

docs/concept/persona/persona-taxonomy.md

@@ -59,7 +59,7 @@ Scheme within a Use Case_
         minimal facts you can use to build your own ontology, schema,
         or graph model.
 
-    ### Required facts about a Persona Taxonomy
+    ### Persona Taxonomy
     - **Opaque universally unique identifier**: A UUID representing this taxonomy.
     - **SKOS Concept Scheme**: Modeled as `skos:ConceptScheme`.
     - **Owned by Use Case**: A reference to the [Use Case](../use-case/index.md) that owns it (zero or one cardinality).

docs/concept/story.md

@@ -218,7 +218,7 @@ defines what a Persona needs to accomplish within a Use Case_
         minimal facts you can use to build your own ontology, schema,
         or graph model.
 
-    ### Required facts about a Story
+    ### Story
 
     - **Opaque universally unique identifier**
         - A Story must have an **opaque**, **universally unique** identifier.

docs/concept/term/business-term.md

@@ -65,7 +65,7 @@ policies_
         minimal facts you can use to build your own ontology, schema,
         or graph model.
 
-    ### Required facts about a Business Term
+    ### Business Term
     - **Inherits from Term**: All facts required for a [Term](index.md#ontology) (UUID, lexical forms, ownership) apply here.
     - **Term Kind**: Must be identified as a "Business Term".
     - **Language**: Should include a natural language tag (e.g., `en`, `nl`).