Fix documentation folder

Author: keveleigh

…umentation/Images/ColorThemeItemData.png …mentation~/Images/ColorThemeItemData.pngorg.mixedrealitytoolkit.theming/~Documentation/Images/ColorThemeItemData.png renamed to org.mixedrealitytoolkit.theming/Documentation~/Images/ColorThemeItemData.png org.mixedrealitytoolkit.theming/~Documentation/Images/ColorThemeItemData.png renamed to org.mixedrealitytoolkit.theming/Documentation~/Images/ColorThemeItemData.png

@@ -1,4 +1,4 @@
-# MRTK Theming 3.0
+# MRTK UX Theming
 
 ## Overview
 
@@ -10,22 +10,22 @@ The system has three layers:
 |---|---|---|
 | **Schema** | `ThemeDataSource` + `ThemeDefinition` | Declares what named items exist and what type each one is |
 | **Values** | `Theme` (ScriptableObject) | Provides a concrete value for every item in the definition |
-| **Binding** | `DataBinding` (MonoBehaviour) + binders | Connects a theme item to a specific component on a GameObject |
+| **Binding** | `ThemeBinding` (MonoBehaviour) + binders | Connects a theme item to a specific component on a GameObject |
 
 ---
 
 ## Theme data source
 
 A `ThemeDataSource` ScriptableObject is the single source of truth for which theme is currently active. Create one per logical theme domain (e.g. one for the whole app, or one per scene).
 
-![ThemeDataSource](./~Documentation/Images/ThemeDataSource.png)
+![ThemeDataSource](./Documentation~/Images/ThemeDataSource.png)
 
 The `ThemeDataSource` holds:
 
 - **`activeTheme`** — the currently applied `Theme` asset.
 - **`themeDefinition`** — the schema that all compatible themes must conform to.
 
-To switch themes at runtime, assign a new `Theme` to `themeDataSource.value`. Every `DataBinding` component subscribed to that source will immediately receive and apply the new values.
+To switch themes at runtime, assign a new `Theme` to `themeDataSource.value`. Every `ThemeBinding` component subscribed to that source will immediately receive and apply the new values.
 
 ### Theme definition
 
@@ -36,32 +36,34 @@ Each item has:
 - **Name** — a string key used to match binders to values at runtime (e.g. `"Primary Color"`, `"Backplate Material"`).
 - **Data type** — a concrete subclass of `BaseThemeItemData<T>` (e.g. `ColorThemeItemData`, `MaterialThemeItemData`).
 
+![ColorThemeItemData](./Documentation~/Images/ColorThemeItemData.png)
+
 ---
 
 ## Theme
 
 A `Theme` ScriptableObject is assigned to a `ThemeDataSource` and provides a concrete value for every item declared in that source's `ThemeDefinition`.
 
-![TextColorMapping](./~Documentation/Images/TextColorMapping.png)
+![TextColorMapping](./Documentation~/Images/TextColorMapping.png)
 
 The `Theme` inspector automatically displays one field per definition item, typed correctly. Themes are **complete** — every item in the definition must have a value. This ensures that switching themes always fully overwrites every bound property, with no leftover values from a previous theme.
 
 ---
 
-## Data binding
+## Theme binding
 
-The `DataBinding` MonoBehaviour connects a `ThemeDataSource` to one or more components on the same GameObject (or its children). Add it to any GameObject that should respond to theme changes.
+The `ThemeBinding` MonoBehaviour connects a `ThemeDataSource` to one or more components on the same GameObject (or its children). Add it to any GameObject that should respond to theme changes.
 
-![DataBindingThemeSource](./~Documentation/Images/DataBindingThemeSource.png)
+![ThemeBindingThemeSource](./Documentation~/Images/ThemeBindingThemeSource.png)
 
-`DataBinding` holds:
+`ThemeBinding` holds:
 
 - **`themeDataSource`** — the source to subscribe to.
 - **`binders`** — a list of `IBinder` implementations, each connecting one theme item to one component.
 
 On `OnEnable`, each binder subscribes to the data source and immediately receives the current theme. On `OnDisable`, binders unsubscribe.
 
-![DataBinding](./~Documentation/Images/DataBinding.png)
+![ThemeBinding](./Documentation~/Images/ThemeBinding.png)
 
 ### Theme binders
 
@@ -122,15 +124,15 @@ public class MyCustomBinder : BaseThemeBinder<Color, MyComponent>
 }
 ```
 
-The new binder will automatically appear in the `DataBinding` binder type dropdown in the Inspector, and the **Bound Theme Item** dropdown will show only the definition items whose data type is compatible with `T`.
+The new binder will automatically appear in the `ThemeBinding` binder type dropdown in the Inspector, and the **Bound Theme Item** dropdown will show only the definition items whose data type is compatible with `T`.
 
 ---
 
 ## How theme switching works at runtime
 
 1. `themeDataSource.value = newTheme` is called.
 2. `ThemeDataSource` fires a `ChangeEvent<Theme>` to all listeners.
-3. Each `DataBinding` component's binders receive the event via `OnThemeChanged`.
+3. Each `ThemeBinding` component's binders receive the event via `OnThemeChanged`.
 4. Each binder calls `Theme.TryGetItemData(ThemeDefinitionItemName, ...)` to look up its value.
 5. If found, `Apply` is called with the new value. If not found, a warning is logged.