From 97d6e652c82397563e299306373b721e928b42da Mon Sep 17 00:00:00 2001 From: Ninosaurier Date: Mon, 7 Sep 2026 12:24:43 +0200 Subject: [PATCH] chore(doc): Fixed typos --- .../adm/business-architecture.mdx | 2 +- .../adm/information-systems-architecture.mdx | 24 ++++++++++----- .../docs/architecture/adm/introduction.mdx | 4 ++- .../adm/technology-architecture.mdx | 29 +++++++++++++------ 4 files changed, 40 insertions(+), 19 deletions(-) diff --git a/docs/src/content/docs/architecture/adm/business-architecture.mdx b/docs/src/content/docs/architecture/adm/business-architecture.mdx index 3afd91a..069eab6 100644 --- a/docs/src/content/docs/architecture/adm/business-architecture.mdx +++ b/docs/src/content/docs/architecture/adm/business-architecture.mdx @@ -194,4 +194,4 @@ The Business Architecture defines: - Strict separation of responsibilities - Accessibility as cross-cutting concern -*(Ensures consistency with Phase C decisions)* \ No newline at end of file +*(Ensures consistency with Phase C _"Information Systems Architecture"_ decisions)* \ No newline at end of file diff --git a/docs/src/content/docs/architecture/adm/information-systems-architecture.mdx b/docs/src/content/docs/architecture/adm/information-systems-architecture.mdx index b6668d5..2e03b14 100644 --- a/docs/src/content/docs/architecture/adm/information-systems-architecture.mdx +++ b/docs/src/content/docs/architecture/adm/information-systems-architecture.mdx @@ -9,9 +9,12 @@ import { Aside } from '@astrojs/starlight/components'; ## 1. Overview -This Application Architecture defines how LUNA Charts is structured at the application level. It describes the internal processing model, developer interaction boundaries, system layers, and architectural style used to ensure accessible, consistent, and predictable chart rendering. +This Application Architecture defines how LUNA Charts is structured at the application level. +It describes the internal processing model, developer interaction boundaries, system layers, and architectural +style used to ensure accessible, consistent, and predictable chart rendering. -LUNA Charts is designed as a declarative, component-based charting library with a controlled internal processing pipeline and strict input boundaries. +LUNA Charts is designed as a declarative, component-based charting library with a controlled internal processing pipeline +and strict input boundaries. ## 2. Architectural Style @@ -62,7 +65,7 @@ Developers cannot: ## 4. System Boundary Model -LUNA Charts exposes a strict system boundary: +LUNA Charts exposes a strict system boundary. ### Allowed Inputs @@ -92,15 +95,18 @@ Receives component input, accepts data and configuration, and normalizes incomin ### 5.2 Resilience & Validation Layer -Validates input data integrity, detects missing or invalid values, triggers fallback behavior if necessary, and emits warnings for developer feedback. +Validates input data integrity, detects missing or invalid values, triggers fallback behavior if necessary, +and emits warnings for developer feedback. ### 5.3 Configuration Resolution Layer -Merges user configuration with default values, resolves themes, labels, and styling parameters, and applies library-provided defaults when needed. +Merges user configuration with default values, resolves themes, labels, and styling parameters, and applies +library-provided defaults when needed. ### 5.4 Accessibility Enforcement Layer -Applies accessibility rules and guidance mechanisms intended to support WCAG-compliant chart implementations, generates ARIA attributes, validates known accessibility constraints, and provides runtime warnings and developer feedback. +Applies accessibility rules and guidance mechanisms intended to support WCAG-compliant chart implementations, +generates ARIA attributes, validates known accessibility constraints, and provides runtime warnings and developer feedback.