DOCS: Change "see" to "refer to"

[amanda-butler-unity]

Change instances of "see" to "refer to" to match our style guide.

Description

Makes minor copy edits.

Testing status & QA

N/A - docs-only change

Overall Product Risks

Please rate the potential complexity and halo effect from low to high for the reviewers. Note down potential risks to specific Editor branches if any.

• Complexity: 0
• Halo Effect: 0

Comments to reviewers

I was comparing Claude with Cursor and used the Input System documentation as a test. If this PR is useful, please feel free to review it. If it conflicts with your in-progress work, please reject it, and I'll close it. Thank you!

Checklist

Before review:

• Changelog entry added.
  • Explains the change in Changed, Fixed, Added sections.
  • For API change contains an example snippet and/or migration example.
  • JIRA ticket linked, example (case %%). If it is a private issue, just add the case ID without a link.
  • Jira port for the next release set as "Resolved".
• Tests added/changed, if applicable.
  • Functional tests Area_CanDoX, Area_CanDoX_EvenIfYIsTheCase, Area_WhenIDoX_AndYHappens_ThisIsTheResult.
  • Performance tests.
  • Integration tests.
• Docs for new/changed API's.
  • Xmldoc cross references are set correctly.
  • Added explanation how the API works.
  • Usage code examples added.
  • The manual is updated, if needed.

During merge:

• Commit message for squash-merge is prefixed with one of the list:
  • NEW: ___.
  • FIX: ___.
  • DOCS: ___.
  • CHANGE: ___.
  • RELEASE: 1.1.0-preview.3.

[u-pr]

The documentation review has identified several technical inaccuracies and minor editorial issues. The main findings include incorrect API usage in migration examples and conceptual errors regarding input action types. Additionally, several typos and formatting inconsistencies were found across multiple documentation files.

_{🤖 Helpful? 👍/👎}

[u-pr]

The mapping for Input.gyro.enabled contains technical errors. InputDevice (and thus Gyroscope) does not have an enabled property; instead, you should use InputSystem.IsDeviceEnabled(device). Additionally, the EnableDevice and DisableDevice methods are static members of the InputSystem class and should be prefixed accordingly for the snippet to be valid code.

Suggested change

[`Input.gyro.enabled`](https://docs.unity3d.com/ScriptReference/Gyroscope-enabled.html)|Get: `Gyroscope.current.enabled`<br/>Set:<br/>`EnableDevice(Gyroscope.current);`<br/>`DisableDevice(Gyroscope.current);`<br/><br/>__Note__: The new Input System replaces `UnityEngine.Gyroscope` with multiple separate sensor devices. Substitute [`Gyroscope`](xref:UnityEngine.InputSystem.Gyroscope) with other sensors in the sample as needed. Refer to the notes for `Input.gyro` above for details.

Get: `InputSystem.IsDeviceEnabled(Gyroscope.current)`<br/>Set:<br/>`InputSystem.EnableDevice(Gyroscope.current);`<br/>`InputSystem.DisableDevice(Gyroscope.current);`<br/><br/>__Note__: The new Input System replaces `UnityEngine.Gyroscope` with multiple separate sensor devices. Substitute [`Gyroscope`](xref:UnityEngine.InputSystem.Gyroscope) with other sensors in the sample as needed. Refer to the notes for `Input.gyro` above for details.

_{🤖 Helpful? 👍/👎}

[u-pr]

The statement that Button type Actions can only be bound to ButtonControl Controls is incorrect. In the Input System, Button actions can be bound to any control that can be represented as a float (such as an axis or a stick magnitude). The system uses the press threshold to determine the interaction state for non-button controls.

Suggested change

This is very similar to [`Value`](xref:UnityEngine.InputSystem.InputActionType.Value), but [`Button`](xref:UnityEngine.InputSystem.InputActionType.Button) type Actions can only be bound to [`ButtonControl`](xref:UnityEngine.InputSystem.Controls.ButtonControl) Controls, and don't perform an initial state check like [`Value`](xref:UnityEngine.InputSystem.InputActionType.Value) Actions do (refer to the Value section above). Use this for inputs that trigger an Action once every time they are pressed. The initial state check is usually not useful in such cases, because it can trigger actions if the button is still held down from a previous press when the Action was enabled.

This is very similar to [`Value`](xref:UnityEngine.InputSystem.InputActionType.Value), but [`Button`](xref:UnityEngine.InputSystem.InputActionType.Button) type Actions don't perform an initial state check like [`Value`](xref:UnityEngine.InputSystem.InputActionType.Value) Actions do (refer to the Value section above). Use this for inputs that trigger an Action once every time they are pressed. The initial state check is usually not useful in such cases, because it can trigger actions if the button is still held down from a previous press when the Action was enabled.

_{🤖 Helpful? 👍/👎}

[u-pr]

This description appears to be a copy-paste error from the Accelerometer section. In the context of the LinearAccelerationSensor documentation, the text should refer to the linear acceleration sensor rather than the raw accelerometer, as the latter includes the effect of gravity and is a separate device type.

Suggested change

Use the accelerometer to measure the acceleration of a device. This is useful to control content by moving a device around. Linear acceleration is the acceleration of a device unaffected by gravity. This is usually derived from a hardware `Accelerometer`, by subtracting the effect of gravity (refer to `GravitySensor`). Values are affected by the [__Compensate Orientation__](xref:input-system-settings#compensate-orientation) setting.

Use the linear acceleration sensor to measure the acceleration of a device. This is useful to control content by moving a device around. Linear acceleration is the acceleration of a device unaffected by gravity. This is usually derived from a hardware `Accelerometer`, by subtracting the effect of gravity (refer to `GravitySensor`). Values are affected by the [__Compensate Orientation__](xref:input-system-settings#compensate-orientation) setting.

_{🤖 Helpful? 👍/👎}

[u-pr]

There is a typo in this line: "For more a more flexible workflow". It should probably be "For a more flexible workflow".

Suggested change

	For more a more flexible workflow, refer to the [Actions Workflow](Workflow-Actions.html).
	For a more flexible workflow, refer to the [Actions Workflow](Workflow-Actions.html).

_{🤖 Helpful? 👍/👎}

[u-pr]

There is an extra space between "the" and "[notification behaviors]".

Suggested change

	3. Set up Action responses, by selecting a **Behavior** type from the Behavior menu. The Behavior type you select affects how you should implement the methods that handle your Action responses. Refer to the [notification behaviors](#notification-behaviors) section further down for details.<br/><br/><br/><br/>
	3. Set up Action responses, by selecting a **Behavior** type from the Behavior menu. The Behavior type you select affects how you should implement the methods that handle your Action responses. Refer to the [notification behaviors](#notification-behaviors) section further down for details.<br/><br/><br/><br/>

_{🤖 Helpful? 👍/👎}

[u-pr]

Have you considered fixing the typo "advisible" to "advisable"? Also, the end of the sentence appears to be missing a verb; it should likely be "...the default map that Player Input uses during Start()." or similar.

Suggested change

	> Currently, when using project-wide actions all the action maps are enabled by default. It is advisible to manually disable them and manually enable the default map that **Player Input** during `Start()`.
	> Currently, when using project-wide actions all the action maps are enabled by default. It is advisable to manually disable them and manually enable the default map that **Player Input** uses during `Start()`.

_{🤖 Helpful? 👍/👎}

[codecov-github-com]

Codecov Report

All modified and coverable lines are covered by tests ✅

@@             Coverage Diff             @@
##           develop    #2404      +/-   ##
===========================================
- Coverage    77.92%   77.40%   -0.52%     
===========================================
  Files          482      483       +1     
  Lines        97755    98577     +822     
===========================================
+ Hits         76175    76306     +131     
- Misses       21580    22271     +691     

Flag	Coverage Δ
inputsystem_Windows_2022.3	5.34% <ø> (-0.22%)	⬇️
inputsystem_Windows_6000.0	5.31% <ø> (-0.03%)	⬇️
inputsystem_Windows_6000.3	5.31% <ø> (-0.03%)	⬇️
inputsystem_Windows_6000.6	5.30% <ø> (-0.04%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 3 files with indirect coverage changes

ℹ️ Need help interpreting these results?