chore(creating-ps-pester-tests): Improve wording

DevTKSS · DevTKSS · commit ff1cf98277c4 · 2025-06-19T21:10:33.000+02:00
Co-authored-by: Agnès ZITTE <16295702+agneszitte@users.noreply.github.com> docs(check_toc): Added documentation to commit 1828cff including troubleshooting gif chore(creating-ps-pester-tests): Improve wording Co-authored-by: Agnès ZITTE <16295702+agneszitte@users.noreply.github.com> chore: applied xref links chore: Fix Title Missing and fix markdownlint chore: applied xref links
diff --git a/doc/articles/check-toc-utilities/Overview.md b/doc/articles/check-toc-utilities/Overview.md
@@ -1,10 +1,9 @@
 ---
 uid: Uno.Contributing.check-toc.Overview
 ---
+# Overview
 
-# Toc Checker Overview
-
-The `check_toc.ps1` script helps maintain the structure and integrity of your documentation by:
+The [`check_toc.ps1`](../check_toc.ps1) script helps maintain the structure and integrity of your documentation by:
 
 - Detecting **broken links** in [toc.yml](../toc.yml)
 - Identifying **Markdown files** recursive to `articles` folder that are **not referenced** in the TOC
@@ -16,7 +15,7 @@ The `check_toc.ps1` script helps maintain the structure and integrity of your do
 ## 🛠️ Usage
 
 1. Open a **PowerShell terminal** at the **root** of your locally cloned Uno repository.
-2. Navigate to the `doc/articles` directory:
+2. Navigate to the [`doc/articles`](../../articles/) directory:
 
    ```ps1
    cd doc/articles
@@ -57,4 +56,4 @@ Utility functions are dynamically imported from [`Import-TocCheckerUtils.ps1`](.
 
 ## 🌐 Further Reading
 
-- [!INCLUDE [Clean Architecture Principles Inline](../includes/clean-architecture-principles-inline.md)]
+- [!INCLUDE [Clean Architecture Principles Inline](xref:Uno.Clean-Architecture-Inline)]
diff --git a/doc/articles/check-toc-utilities/Utilities.md b/doc/articles/check-toc-utilities/Utilities.md
@@ -5,7 +5,7 @@ uid: Uno.Contributing.check-toc.Utilities
 
 *[SoC]: Separation of Concerns – Part of Clean Architecture
 
-The utility functions used by the `check_toc.ps1` script follow SoC principles to improve modularity, maintainability, and testability. These helpers are dynamically imported during script execution via the [`Import-TocCheckerUtils.ps1`](../check-toc-utilities/Import-TocCheckerUtils.ps1) script and encapsulate common logic such as file enumeration, header parsing, and output generation.
+The utility functions used by the `check_toc.ps1` script follow SoC principles to improve modularity, maintainability, and testability. These helpers are dynamically imported during script execution via the [`Import-TocCheckerUtils.ps1`](./Import-TocCheckerUtils.ps1) script and encapsulate common logic such as file enumeration, header parsing, and output generation.
 
 > [!TIP]
 > Keeping utility functions well-documented and separated from the main script logic helps contributors understand, maintain, and extend the tooling efficiently.
diff --git a/doc/articles/contributing/Documentation/docfx.md b/doc/articles/contributing/Documentation/docfx.md
@@ -178,4 +178,4 @@ To run the script on Windows:
 
 ## Import Uno Extensions and Tools docs
 
-[!INCLUDE ../external/  <!--https://github.com/unoplatform/uno.extensions/blob/main/doc/README.md -->]
+[!INCLUDE [Import external docs](../../external/uno.extensions/doc/README.md)]
diff --git a/doc/articles/contributing/guidelines/creating-ps-pester-tests.md b/doc/articles/contributing/guidelines/creating-ps-pester-tests.md
@@ -6,7 +6,7 @@ uid: Uno.Contributing.Scripts.PowerShell-Pester-Tests
 
 ## Introduction
 
-Some Parts of Uno.UI like the [Toc Checker](xref:Uno.Contributing.check-toc.Overview) with its [Utility Functions](xref:Uno.Contributing.check-toc.Utilities) are written in PowerShell. To make sure, they are working properly, the recommended and most common used Testing Framework is [Pester](https://pester.dev/docs/quick-start).
+Some Parts of Uno.UI like the [Toc Checker](xref:Uno.Contributing.check-toc.Overview) with its [Utility Functions](xref:Uno.Contributing.check-toc.Utilities) are written in PowerShell. To make sure they are working properly, the recommended and most commonly used Testing Framework is [Pester](https://pester.dev/docs/quick-start).
 
 <!-- ### TODO: ## Installing Pester 5+ https://pester.dev/docs/introduction/installation -->
 
diff --git a/doc/articles/guides/how-to-create-control-libraries.md b/doc/articles/guides/how-to-create-control-libraries.md
@@ -105,7 +105,7 @@ In a Control Class Library, [conditional XAML](xref:Uno.Development.PlatformSpec
 
 ## Library assets
 
-WinUI 3 and Uno Platform (4.6 and later) Libraries support the inclusion of content assets to be used with [`StorageFile.GetFileFromApplicationUriAsync`](../features/file-management.md#support-for-storagefilegetfilefromapplicationuriasync), as well as with the `ms-appx:///[libraryname]/[assetname_file_name]` format.
+WinUI 3 and Uno Platform (4.6 and later) Libraries support the inclusion of content assets to be used with [`StorageFile.GetFileFromApplicationUriAsync`](xref:Uno.Features.FileManagement#support-for-storagefilegetfilefromapplicationuriasync), as well as with the `ms-appx:///[libraryname]/[assetname_file_name]` format.
 
 > [!IMPORTANT]
 > When using library assets with non-WinAppSDK targets, the library name should also be lower cased.
@@ -126,7 +126,7 @@ In both cases, for the build system to include the assets files, the following p
 ```
 
 > [!IMPORTANT]
-> WinAppSDK [does not support assets](https://github.com/microsoft/microsoft-ui-xaml/issues/6429) if the application is using the MSIX package mode. To use the unpackaged mode, [see this article](../features/winapp-sdk-specifics.md#unpackaged-application-support).
+> WinAppSDK [does not support assets](https://github.com/microsoft/microsoft-ui-xaml/issues/6429) if the application is using the MSIX package mode. To use the unpackaged mode, [see this article](xref:Uno.Features.WinAppSDK#un-packaged-application-support).
 
 ## Considerations for the Skia Renderer
 
diff --git a/doc/articles/includes/clean-architecture-principles-inline.md b/doc/articles/includes/clean-architecture-principles-inline.md
@@ -1,2 +1,5 @@
+---
+uid: Uno.Clean-Architecture-Inline
+---
 <!-- markdownlint-disable MD041-->
 [Clean Architecture principles](https://devblogs.microsoft.com/ise/next-level-clean-architecture-boilerplate)
diff --git a/doc/articles/toc.yml b/doc/articles/toc.yml
@@ -165,7 +165,7 @@
           - name: Working with Skia Desktop
             href: xref:Uno.Skia.Desktop
           - name: Working with the Linux Framebuffer
-            href: features/using-linux-framebuffer.md
+            href: xref:Uno.Skia.Linux.Framebuffer
         - name: Philosophy
           href: xref:Uno.Overview.Philosophy
         - name: How Uno Works
@@ -192,9 +192,9 @@
       - name: Creating Custom Controls
         href: guides/creating-custom-controls.md
       - name: Control Libraries
-        href: guides/how-to-create-control-libraries.md
+        href: xref:Guide.HowTo.Create-Control-Library
       - name: Adding New Platforms
-        href: guides/how-to-add-platforms-existing-project.md
+        href: xref:Uno.Guides.AddAdditionalPlatforms
       - name: Using the Skia Desktop
         href: xref:Uno.Skia.Desktop
       - name: Linux Framebuffer
@@ -322,9 +322,9 @@
         - name: IL Linker for WebAssembly
           href: xref:uno.articles.features.illinker
         - name: Working with String Resource Trimming
-          href: features/upri-trimming.md
+          href: xref:Uno.Features.StringResourceTrimming
         - name: Working with XAML Trimming
-          href: features/resources-trimming.md
+          href: xref:Uno.Features.ResourcesTrimming
         - name: Error Monitoring & Crash Reporting with Raygun
           href: xref:Monitoring.Raygun
 
@@ -365,7 +365,7 @@
       - name: Guidelines for Contributing Documentation
         items:
         - name: Adding documentation
-          href: uno-development/doc-on-docs.md
+          href: xref:Uno.Contributing.Docs
         - name: DocFX
           href: xref:Uno.Contributing.DocFx
         - name: Toc Checker
@@ -481,7 +481,7 @@
         - name: Uno and WinUI 3
           href: uwp-vs-winui3.md
         - name: WinAppSDK Specifics
-          href: features/winapp-sdk-specifics.md
+          href: xref:Uno.Features.WinAppSDK
         - name: WinUI links
           items:
             - name: Overview
@@ -507,19 +507,19 @@
             - name: Activities in Android
               href: android-activities.md
             - name: ComboBox
-              href: controls/ComboBox.md
+              href: xref:Uno.Controls.ComboBox
             - name: CommandBar
-              href: controls/CommandBar.md
+              href: xref:Uno.Controls.CommandBar
             - name: DatePicker
-              href: controls/DatePicker.md
+              href: xref:Uno.Controls.DatePicker
             - name: ElevatedView
-              href: features/ElevatedView.md
+              href: xref:Uno.Features.ElevatedView
             - name: Fluent icon font
-              href: uno-fluent-assets.md
+              href: xref:Uno.Development.FluentAssets
             - name: Flyout
-              href: controls/Flyout.md
+              href: xref:Uno.Controls.Flyout
             - name: Frame
-              href: controls/Frame.md
+              href: xref:Uno.Controls.Frame
             - name: GLCanvasElement
               href: xref:Uno.Controls.GLCanvasElement
             - name: Image
diff --git a/doc/articles/uno-development/assets/check-toc-find-toc-additions-file.gif b/doc/articles/uno-development/assets/check-toc-find-toc-additions-file.gif

Original file line number	Diff line number	Diff line change
`@@ -178,4 +178,4 @@ To run the script on Windows:`
`178`	`178`
`179`	`179`	`## Import Uno Extensions and Tools docs`
`180`	`180`
`181`		`-[!INCLUDE ../external/ <!--https://github.com/unoplatform/uno.extensions/blob/main/doc/README.md -->]`
	`181`	`+[!INCLUDE [Import external docs](../../external/uno.extensions/doc/README.md)]`