docs (style - PVP)

Resolving more white space issues.

Author: NoelStephensUnity

com.unity.netcode.gameobjects/Documentation~/components/Helpers/componentcontroller.md

@@ -6,8 +6,7 @@ The `ComponentController` can be:
 - Used with `AttachableBehaviour` or independently for another purpose.
 - Configured to directly or inversely follow the `ComponentController`'s current state.
 - Configured to have an enable and/or disable delay.
-  -  _When invoked internally by `AttachableBehaviour`, delays are ignored when an `AttachableNode` is being destroyed and the changes are immediate._
-
+  - _When invoked internally by `AttachableBehaviour`, delays are ignored when an `AttachableNode` is being destroyed and the changes are immediate._
 
 ## Configuring
 
@@ -21,7 +20,6 @@ A `ComponentController` can have one or more `ComponentEntry` entries in its **C
 
 Both delay values (Enable & Disable) has many uses, but an example would be to prevent a `MeshRenderer` from being enabled prior to other specific events like avoiding it from rendering for a few frames while the attachable is positioned.
 
-
 ## Examples
 
 ### Independent Usage
@@ -60,15 +58,15 @@ public class DaisyChainedController : MonoBehaviour
 The above component could be arranged to create a chained sequence of components when the root `DaisyChainedController` component is enabled or disabled. Such a sequence could look like:
 
 - DaisyChainedController-A
-  - Controller 
+  - Controller
     - Points to DaisyChainedController-B
 - DaisyChainedController-B
-  - Controller 
+  - Controller
     - Points to DaisyChainedController-C
 - DaisyChainedController-C
-  - Controller 
+  - Controller
 
-When DaisyChainedController-A is enabled, then a sequence of events would occur where DaisyChainedController-B and DaisyChainedController-C would be enabled. The same sequence of events would occur when DaisyChainedController-A was then disabled. 
+When DaisyChainedController-A is enabled, then a sequence of events would occur where DaisyChainedController-B and DaisyChainedController-C would be enabled. The same sequence of events would occur when DaisyChainedController-A was then disabled.
 
 ### AttachableBehaviour Usage
 

com.unity.netcode.gameobjects/Documentation~/components/foundational/networkbehaviour-synchronize.md

@@ -103,9 +103,9 @@ Now that you understand the general concept behind `NetworkBehaviour.OnSynchroni
 
 _"When would you want to use `NetworkBehaviour.OnSynchronize`?"_
 
- `NetworkVariable`s can be useful to synchronize state, but they also are only updated every network tick. While it is possible to adjust a `NetworkVariable`'s update frequency, `NetworkVariable`s (in general) guarantees state synchronization but does not guarantee state changes will be updated in the same order they were chanted relative to other `NetworkVariables`.
- 
- With this in mind, you might need states to be updated in the relative order in which they were changed. In order to do this, you can combine the use of an RPC to handle updating the change in a properties state/value while using `NetworkBehaviour.OnSynchronize` to assure that any late joining client will be synchronized with the current state of said property.
+`NetworkVariable`s can be useful to synchronize state, but they also are only updated every network tick. While it is possible to adjust a `NetworkVariable`'s update frequency, `NetworkVariable`s (in general) guarantees state synchronization but does not guarantee state changes will be updated in the same order they were chanted relative to other `NetworkVariables`.
+
+With this in mind, you might need states to be updated in the relative order in which they were changed. In order to do this, you can combine the use of an RPC to handle updating the change in a properties state/value while using `NetworkBehaviour.OnSynchronize` to assure that any late joining client will be synchronized with the current state of said property.
 
 **Using a synchronized RPC driven field approach:**
 
@@ -186,7 +186,7 @@ public class SimpleRpcState : NetworkBehaviour
 
     /// <summary>
     /// Late joining clients will be synchronized
-    /// to the most current m_ToggleState
+    /// to the most current m_ToggleState.
     /// </summary>
     protected override void OnSynchronize<T>(ref BufferSerializer<T> serializer)
     {
@@ -201,7 +201,7 @@ public class SimpleRpcState : NetworkBehaviour
 
     /// <summary>
     /// Synchronizes connected clients with the
-    /// server-side m_ToggleState
+    /// server-side m_ToggleState.
     /// </summary>
     /// <param name="stateIsSet"></param>
     [Rpc(SendTo.ClientsAndHost)]