improve documentation

Author: bmalrat

Packages/com.unity.inputsystem/InputSystem/Actions/Composites/ButtonWithTwoModifiers.cs

@@ -98,7 +98,7 @@ public class ButtonWithTwoModifiers : InputBindingComposite<float>
         /// By default, if the setting <see cref="InputSettings.shortcutKeysConsumeInput"/> is enabled,
         /// <see cref="modifier1"/> and <see cref="modifier2"/> are required to be in pressed state before or at the same
         /// time that <see cref="button"/> goes into pressed state for the composite as a whole to trigger. This means that binding to,
-        /// for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> <c>shift</c> keys have to be pressed before pressing the <c>B</c> key.
+        /// for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> and <c>shift</c> keys have to be pressed, in any order,  before pressing the <c>B</c> key.
         /// This is the behavior usually expected with keyboard shortcuts.
         ///
         /// This parameter can be used to bypass this behavior and allow any timing between <see cref="modifier1"/>, <see cref="modifier2"/>,
@@ -119,7 +119,7 @@ public enum ModifiersOrder
             /// By default, if the setting <see cref="InputSettings.shortcutKeysConsumeInput"/> is enabled,
             /// <see cref="modifier1"/> and <see cref="modifier2"/> are required to be in pressed state before or at the same
             /// time that <see cref="button"/> goes into pressed state for the composite as a whole to trigger. This means that binding to,
-            /// for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> <c>shift</c> keys have to be pressed before pressing the <c>B</c> key.
+            /// for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> and <c>shift</c> keys have to be pressed, in any order, before pressing the <c>B</c> key.
             /// This is the behavior usually expected with keyboard shortcuts.
             ///
             /// If the setting <see cref="InputSettings.shortcutKeysConsumeInput"/> is disabled,
@@ -130,7 +130,7 @@ public enum ModifiersOrder
             /// <summary>
             /// <see cref="modifier1"/> and <see cref="modifier2"/> are required to be in pressed state before or at the same
             /// time that <see cref="button"/> goes into pressed state for the composite as a whole to trigger. This means that binding to,
-            /// for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> <c>shift</c> keys have to be pressed before pressing the <c>B</c> key.
+            /// for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> and <c>shift</c> keys have to be pressed, in any order,  before pressing the <c>B</c> key.
             /// This is the behavior usually expected with keyboard shortcuts.
             /// </summary>
             Ordered = 1,
@@ -149,7 +149,7 @@ public enum ModifiersOrder
         /// By default, if the setting <see cref="InputSettings.shortcutKeysConsumeInput"/> is enabled,
         /// <see cref="modifier1"/> and <see cref="modifier2"/> are required to be in pressed state before or at the same
         /// time that <see cref="button"/> goes into pressed state for the composite as a whole to trigger. This means that binding to,
-        /// for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> <c>shift</c> keys have to be pressed before pressing the <c>B</c> key.
+        /// for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> and <c>shift</c> keys have to be pressed, in any order,  before pressing the <c>B</c> key.
         /// This is the behavior usually expected with keyboard shortcuts.
         ///
         /// If the setting <see cref="InputSettings.shortcutKeysConsumeInput"/> is disabled,

Packages/com.unity.inputsystem/InputSystem/Actions/Composites/OneModifierComposite.cs

@@ -128,7 +128,7 @@ public enum ModifiersOrder
             /// <summary>
             /// if <see cref="binding"/> is bound to only <see cref="Controls.ButtonControl"/>s, then the composite requires
             /// <see cref="modifier"/> to be pressed <em>before</em> pressing <see cref="binding"/>. This means that binding to, for example,
-            /// <c>Ctrl+B</c>, the <c>ctrl</c> keys have to be pressed before pressing the <c>B</c> key. This is the behavior usually expected
+            /// <c>Ctrl+B</c>, the <c>ctrl</c> key have to be pressed before pressing the <c>B</c> key. This is the behavior usually expected
             /// with keyboard shortcuts.
             /// </summary>
             Ordered = 1,

Packages/com.unity.inputsystem/InputSystem/Actions/Composites/TwoModifiersComposite.cs

@@ -93,7 +93,7 @@ public class TwoModifiersComposite : InputBindingComposite
         /// By default, if the setting <see cref="InputSettings.shortcutKeysConsumeInput"/> is enabled,
         /// if <see cref="binding"/> is bound to only <see cref="Controls.ButtonControl"/>s, then the composite requires
         /// both <see cref="modifier1"/> and <see cref="modifier2"/> to be pressed <em>before</em> pressing <see cref="binding"/>.
-        /// This means that binding to, for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> and <c>shift</c> keys have to be pressed
+        /// This means that binding to, for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> and <c>shift</c> keys have to be pressed, in any order, 
         /// before pressing the <c>B</c> key. This is the behavior usually expected with keyboard shortcuts.
         ///
         /// However, when binding, for example, <c>Ctrl+Shift+MouseDelta</c>, it should be possible to press <c>ctrl</c> and <c>shift</c>
@@ -119,7 +119,7 @@ public enum ModifiersOrder
             /// By default, if the setting <see cref="InputSettings.shortcutKeysConsumeInput"/> is enabled,
             /// if <see cref="binding"/> is bound to only <see cref="Controls.ButtonControl"/>s, then the composite requires
             /// both <see cref="modifier1"/> and <see cref="modifier2"/> to be pressed <em>before</em> pressing <see cref="binding"/>.
-            /// This means that binding to, for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> and <c>shift</c> keys have to be pressed
+            /// This means that binding to, for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> and <c>shift</c> keys have to be pressed, in any order, 
             /// before pressing the <c>B</c> key. This is the behavior usually expected with keyboard shortcuts.
             ///
             /// If the setting <see cref="InputSettings.shortcutKeysConsumeInput"/> is disabled,
@@ -130,7 +130,7 @@ public enum ModifiersOrder
             /// <summary>
             /// if <see cref = "binding" /> is bound to only <see cref = "Controls.ButtonControl" /> s, then the composite requires
             /// both <see cref="modifier1"/> and <see cref="modifier2"/> to be pressed <em>before</em> pressing <see cref="binding"/>.
-            /// This means that binding to, for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> and <c>shift</c> keys have to be pressed
+            /// This means that binding to, for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> and <c>shift</c> keys have to be pressed, in any order, 
             /// before pressing the <c>B</c> key. This is the behavior usually expected with keyboard shortcuts.
             /// </summary>
             Ordered = 1,
@@ -149,7 +149,7 @@ public enum ModifiersOrder
         /// By default, if the setting <see cref="InputSettings.shortcutKeysConsumeInput"/> is enabled,
         /// if <see cref="binding"/> is bound to only <see cref="Controls.ButtonControl"/>s, then the composite requires
         /// both <see cref="modifier1"/> and <see cref="modifier2"/> to be pressed <em>before</em> pressing <see cref="binding"/>.
-        /// This means that binding to, for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> and <c>shift</c> keys have to be pressed
+        /// This means that binding to, for example, <c>Ctrl+Shift+B</c>, the <c>ctrl</c> and <c>shift</c> keys have to be pressed, in any order, 
         /// before pressing the <c>B</c> key. This is the behavior usually expected with keyboard shortcuts.
         ///
         /// If the setting <see cref="InputSettings.shortcutKeysConsumeInput"/> is disabled,