Removing some images

suearkinunity · suearkinunity · commit cac1d2ffc583 · 2026-07-08T12:26:28.000+01:00
diff --git a/Packages/com.unity.inputsystem/Documentation~/Settings.md b/Packages/com.unity.inputsystem/Documentation~/Settings.md
@@ -4,6 +4,4 @@ uid: input-system-settings
 
 To configure the Input System individually for each project, go to __Edit__ > __Project Settings…__ > __Input System Package__ from Unity's main menu.
 
-![Input Settings](Images/InputSettings.png)
-
 This section describes each input setting in detail.
diff --git a/Packages/com.unity.inputsystem/Documentation~/debug-layouts.md b/Packages/com.unity.inputsystem/Documentation~/debug-layouts.md
@@ -6,4 +6,3 @@ uid: input-system-debug-layouts
 
 The [__Layouts__](layouts.md) list in the Input Debugger window displays a breakdown of all registered [Control and Device layouts](layouts.md). This is the database of supported hardware and the knowledge of how to represent a given piece of input hardware. It's useful when you want to [create a new Device mapping](hid-create-custom-layout.md) and see how the Input System represents it.
 
-![Layouts in Input Debugger](Images/LayoutsInDebugger.png)
diff --git a/Packages/com.unity.inputsystem/Documentation~/debug-users-playerinput.md b/Packages/com.unity.inputsystem/Documentation~/debug-users-playerinput.md
@@ -6,4 +6,3 @@ uid: input-system-debug-users-playerinput
 
 When there are [`InputUser`](user-management.md) instances (if you use `PlayerInput`, each `PlayerInput` instance implicitly creates one), the Input Debugger's __Users__ list displays each instance along with its paired Devices and active Actions. The listed Devices and Actions work the same way as those displayed in the [__Devices__](debug-device.md) and [__Actions__](debug-action.md) lists in the debugging window.
 
-![Users in Input Debugger](Images/UsersInputDebugger.png)
diff --git a/Packages/com.unity.inputsystem/Documentation~/supported-devices.md b/Packages/com.unity.inputsystem/Documentation~/supported-devices.md
@@ -4,8 +4,6 @@ uid: input-system-supported-devices
 
 # Supported devices
 
-![Supported Devices](Images/SupportedDevices.png)
-
 A Project usually supports a known set of input methods. For example, a mobile app might support only touch, and a console application might support only gamepads. A cross-platform application might support gamepads, mouse, and keyboard, but might not require XR Device support.
 
 To narrow the options that the Editor UI presents to you, and to avoid creating input Devices and consuming input that your application won't use, you can restrict the set of supported Devices on a per-project basis.

Original file line number	Diff line number	Diff line change
`@@ -6,4 +6,3 @@ uid: input-system-debug-layouts`
`6`	`6`
`7`	`7`	`The [__Layouts__](layouts.md) list in the Input Debugger window displays a breakdown of all registered [Control and Device layouts](layouts.md). This is the database of supported hardware and the knowledge of how to represent a given piece of input hardware. It's useful when you want to [create a new Device mapping](hid-create-custom-layout.md) and see how the Input System represents it.`
`8`	`8`
`9`		`-![Layouts in Input Debugger](Images/LayoutsInDebugger.png)`
Original file line number	Diff line number	Diff line change
`@@ -6,4 +6,3 @@ uid: input-system-debug-users-playerinput`
`6`	`6`
`7`	`7`	When there are [`InputUser`](user-management.md) instances (if you use `PlayerInput`, each `PlayerInput` instance implicitly creates one), the Input Debugger's __Users__ list displays each instance along with its paired Devices and active Actions. The listed Devices and Actions work the same way as those displayed in the [__Devices__](debug-device.md) and [__Actions__](debug-action.md) lists in the debugging window.
`8`	`8`
`9`		`-![Users in Input Debugger](Images/UsersInputDebugger.png)`