Use consistent MSXOrg naming

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Author: MariusStorhaug

.github/plugin/psmodule/skills/psmodule-zensical-migration/SKILL.md

@@ -24,7 +24,7 @@ Apply these sources in order:
    is the canonical generated-module profile and the byte-level source for
    module repositories.
 
-MSXorg takes precedence when the first two designs differ. Do not resolve a
+MSXOrg takes precedence when the first two designs differ. Do not resolve a
 difference independently in every consumer. If the generated-module profile
 does not represent the intended design, report the upstream gap and block the
 consumer migration until the Process-PSModule change's template-impact

docs/content/reference/repository-standard.md

@@ -419,8 +419,8 @@ This keeps the repository landing page readable and prevents drift between READM
 The canonical module-site configuration is
 [`Template-PSModule/.github/zensical.toml`](https://github.com/PSModule/Template-PSModule/blob/main/.github/zensical.toml).
 Keep its repository placeholders: Process-PSModule resolves them while staging
-the generated site. The template carries the portable subset of the MSXorg and
-Process-PSModule documentation design, with the MSXorg design taking precedence
+the generated site. The template carries the portable subset of the MSXOrg and
+Process-PSModule documentation design, with the MSXOrg design taking precedence
 when they differ.
 
 Do not declare `nav` in a standard module repository. Zensical derives