Update some file headers

Author: keveleigh

docs/mrtk3-overview/api-reference.md

@@ -3,7 +3,7 @@ title: API reference
 nav_order: 8
 ---
 
-# API reference — MRTK3
+# API reference
 
 MRTK3 is now shipping as [a set of individually versioned packages](index.md#versioning). As a result, each MRTK3 package ships its API reference individually. Please find the links to the API references for MRTK3 packages below:
 

docs/mrtk3-overview/architecture/architecture.md

@@ -3,7 +3,7 @@ title: Architecture overview
 nav_order: 5
 ---
 
-# Architecture overview — MRTK3
+# Architecture overview
 
 ![Architecture MRTK3](../images/MRTK_v3_Architecture.png)
 

docs/mrtk3-overview/architecture/interactables.md

@@ -4,7 +4,7 @@ parent: Architecture overview
 nav_order: 2
 ---
 
-# Interactables — MRTK3
+# Interactables
 
 MRTK builds on the `XRBaseInteractable` provided by Unity's XR Interaction Toolkit. The existing interactable behavior and API is fully supported in MRTK, and all of our custom interactables obey the existing XRI interactable API.
 

docs/mrtk3-overview/architecture/interactors.md

@@ -4,7 +4,7 @@ parent: Architecture overview
 nav_order: 1
 ---
 
-# Interactor Architecture — MRTK3
+# Interactor Architecture
 
 MRTK builds upon the set of interactors offered by Unity's XR Interaction Toolkit. Mixed reality features like articulated hand tracking, gaze, and pinch require more elaborate interactors than the set provided with XRI by default. MRTK defines new interactor interfaces, categorized generally by the input modality, and corresponding implementations.
 

docs/mrtk3-overview/architecture/subsystems.md

@@ -4,7 +4,7 @@ parent: Architecture overview
 nav_order: 3
 ---
 
-# Subsystems — MRTK3
+# Subsystems
 
 MRTK3 leverages the Unity XR Subsystem Management infrastructure for writing extensible modules that can help provide cross-platform support for features like speech and hand tracking. These subsystems are initialized and loaded by Unity alongside the existing Unity-native subsystems like `XRMeshSubsystem` and `XRInputSubsystem`. See [the documentation for how Unity subsystems work](https://docs.unity3d.com/ScriptReference/UnityEngine.SubsystemsModule.html).
 

docs/mrtk3-overview/known-issues.md

@@ -3,6 +3,6 @@ title: Known issues
 nav_order: 7
 ---
 
-# Known issues — MRTK3
+# Known issues
 
 For known issues in MRTK3, refer to [the issues page](https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity/issues?q=is%3Aopen+is%3Aissue) of our GitHub repo.

org.mixedrealitytoolkit.input/Visualizers/RiggedHandVisualizer/README.md

@@ -1,3 +1,5 @@
+# FAQ
+
 ## Why are there three different shaders + materials for the rigged hand?
 
 URP doesn't support multipass shaders, unfortunately! So we have to split the three passes
@@ -15,8 +17,8 @@ render pipelines!
 It's a model that we've had internally for a while (since the early days of MRTK!) It's been
 re-rigged and painted with the correct vertex colors for MRTK3.
 
-## I want hands with a different shader/color/material/model/etc!
+## I want hands with a different shader/color/material/model/etc
 
 Great! You can build your own hand model prefab with your own custom mesh or materials, and
 still use the RiggedHandMeshVisualizer.cs script. The script expects joints/armatures in the
-default Blender format, following OpenXR joint conventions.
+default Blender format, following OpenXR joint conventions.

org.mixedrealitytoolkit.uxcomponents/LICENSE.md

@@ -1,6 +1,6 @@
 BSD 3-Clause License
 
-Copyright (c) 2023, Mixed Reality Toolkit Contributors
+Copyright (c) 2025, Mixed Reality Toolkit Contributors
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are met: