2253, still

Author: suearkinunity

Packages/com.unity.inputsystem/Documentation~/debug-device.md

@@ -6,7 +6,7 @@ uid: input-system-debug-device
 
 In the Input Debugger window, navigate to the __Devices__ list and double-click any [Input Device](devices.md). This opens a window that displays information about the Device, including real-time state information for its Controls.
 
-![Device in Input Debugger](Images/DeviceInDebugger.png)
+![The Unity Editor window displays the Analysis option selected from the Window menu, and the Input Debugger option selected from the Analysis submenu to demonstrate how to access the devices in the Input Debugger tab.](Images/DeviceInDebugger.png)
 
 The top of the Device window displays general information about the specific Device, such as name, manufacturer, and serial number. This section also display the current __sample frequency__ and __processing delay__ of the deivce.
 

Packages/com.unity.inputsystem/Documentation~/device-descriptions.md

@@ -4,9 +4,9 @@ uid: input-system-device-descriptions
 
 # Device descriptions 
 
-An [`InputDeviceDescription`](xref:UnityEngine.InputSystem.Layouts.InputDeviceDescription) describes a Device. The Input System uses this primarily during the Device discovery process. When a new Device is reported (by the runtime or by the user), the report contains a Device description. Based on the description, the system then attempts to find a Device [layout](layouts.md) that matches the description. This process is based on [Device matchers](#matching).
+The Input System uses the device description defined as a [`InputDeviceDescription`](xref:UnityEngine.InputSystem.Layouts.InputDeviceDescription) primarily during the Device discovery process. When a new Device is reported (by the runtime or by the user), the system then attempts to find a Device [layout](layouts.md) that matches the Device description contained in the report. This process is based on [Device matching](#matching).
 
-After a Device has been created, you can retrieve the description it was created from through the [`InputDevice.description`](xref:UnityEngine.InputSystem.InputDevice) property.
+After a Device has been created, you can retrieve the description it was created from through the [`InputDevice.description`](xref:UnityEngine.InputSystem.InputDevice.description) property.
 
 Every description has a set of standard fields:
 

Packages/com.unity.inputsystem/Documentation~/device-matching.md

@@ -23,7 +23,7 @@ InputSystem.RegisterLayoutMatcher<MyDevice>(
 
 ```
 
-If multiple matchers are matching the same [`InputDeviceDescription`](xref:UnityEngine.InputSystem.Layouts.InputDeviceDescription), the Input System chooses the matcher that has the larger number of properties to match against.
+If multiple matchers identify the same [`InputDeviceDescription`](xref:UnityEngine.InputSystem.Layouts.InputDeviceDescription), the Input System chooses the matcher that has the larger number of properties to match against.
 
 ## Hijacking the matching process
 

Packages/com.unity.inputsystem/Documentation~/visualise-actions.md

@@ -6,4 +6,4 @@ uid: input-system-visualise-actions
 
 `InputActionVisualizer` visualizes the current state of a single Action in real time. You can have multiple Action visualizers to visualize the state of multiple Actions. This can also display the current value of the Action and the Control currently driving the Action, and track the state of [Interactions](Interactions.md) over time. Check the `SimpleControlsVisualizer` Scene in the sample for examples.
 
-![InputActionVisualizer](Images/InputActionVisualizer.png)
+![The Fire Action appears in green in the InputActionVisualizer to show it is selected.](Images/InputActionVisualizer.png)

Packages/com.unity.inputsystem/Documentation~/visualise-input-controls.md

@@ -6,4 +6,4 @@ uid: input-system-visualise-input-controls
 
 `InputControlVisualizer` visualizes the current state of a single Control in real time. You can have multiple Control visualizers to visualize the state of multiple Controls. Check the `GamepadVisualizer`, `MouseVisualizer`, or `PenVisualizer` Scenes in the sample for examples.
 
-![InputControlVisualizer](Images/InputControlVisualizer.png)
+![LeftTrigger and Y appear in green in the InputControlVisualizer to show they are selected.](Images/InputControlVisualizer.png)