Fixing PVP errors

Author: jabbacakes

com.unity.netcode.gameobjects/Documentation~/advanced-topics/custom-serialization.md

@@ -44,7 +44,7 @@ You can also optionally use the same method to add support for `BufferSerializer
 ```csharp
 // The class name doesn't matter here.
 public static class SerializationExtensions
-{  
+{
     public static void SerializeValue<TReaderWriter>(this BufferSerializer<TReaderWriter> serializer, ref Url url) where TReaderWriter: IReaderWriter
     {
         if (serializer.IsReader)
@@ -66,7 +66,7 @@ To add custom serialization support in `NetworkVariable`, follow the steps from
 
 ```csharp
 UserNetworkVariableSerialization<Url>.WriteValue = SerializationExtensions.WriteValueSafe;
-UserNetworkVariableSerialization<Url>.ReadValue = SerializationExtensions.ReadValueSafe;    
+UserNetworkVariableSerialization<Url>.ReadValue = SerializationExtensions.ReadValueSafe;
 ```
 
 You can also use lambda expressions here:

com.unity.netcode.gameobjects/Documentation~/advanced-topics/fastbufferwriter-fastbufferreader.md

@@ -25,7 +25,7 @@ void Serialize(FastBufferWriter writer)
 {
     if(!writer.TryBeginWrite(sizeof(float) + sizeof(bool) + sizeof(i)))
     {
-		throw new OverflowException("Not enough space in the buffer");
+        throw new OverflowException("Not enough space in the buffer");
     }
     writer.WriteValue(f);
     writer.WriteValue(b);
@@ -38,7 +38,7 @@ void Serialize(FastBufferWriter writer)
 {
     if(!writer.TryBeginWrite(sizeof(ExampleStruct)))
     {
-		throw new OverflowException("Not enough space in the buffer");
+        throw new OverflowException("Not enough space in the buffer");
     }
     writer.WriteValue(this);
 }
@@ -135,8 +135,8 @@ To address that, `FastBufferReader` and `FastBufferWriter` don't, themselves, ha
 FastBufferWriter writer = new FastBufferWriter(256, Allocator.TempJob);
 using(var bitWriter = writer.EnterBitwiseContext())
 {
-	bitWriter.WriteBit(a);
-	bitWriter.WriteBits(b, 5);
+    bitWriter.WriteBit(a);
+    bitWriter.WriteBits(b, 5);
 } // Dispose automatically adds 2 more 0 bits to pad to the next byte.
 ```
 

com.unity.netcode.gameobjects/Documentation~/advanced-topics/inscene_parenting_player.md

@@ -24,7 +24,7 @@ Here is an example script that we recommend using to achieve this:
 using Unity.Netcode;
 
 public class ParentPlayerToInSceneNetworkObject : NetworkBehaviour
-{   
+{
     public override void OnNetworkSpawn()
     {
         if (IsServer)

com.unity.netcode.gameobjects/Documentation~/advanced-topics/message-system/reliability.md

@@ -20,7 +20,7 @@ void MyReliableServerRpc() { /* ... */ }
 void MyUnreliableServerRpc() { /* ... */ }
 ```
 
-Reliable RPCs will be received on the remote end in the same order they are sent, but this in-order guarantee only applies to RPCs on the same `NetworkObject`. Different `NetworkObjects` might have reliable RPCs called but executed in different order compared to each other. To put more simply, **in-order reliable RPC execution is guaranteed per `NetworkObject` basis only**.  If you determine an RPC is being updated often (that is, several times per second), it _might_ be better suited as an unreliable RPC.    
+Reliable RPCs will be received on the remote end in the same order they are sent, but this in-order guarantee only applies to RPCs on the same `NetworkObject`. Different `NetworkObjects` might have reliable RPCs called but executed in different order compared to each other. To put more simply, **in-order reliable RPC execution is guaranteed per `NetworkObject` basis only**.  If you determine an RPC is being updated often (that is, several times per second), it _might_ be better suited as an unreliable RPC.
 
 > [!NOTE]
 > When testing unreliable RPCs on a local network, the chance of an unreliable packet being dropped is reduced greatly (sometimes never).  As such, you might want to use [`UnityTransport`'s Simulator Pipeline](https://docs-multiplayer.unity3d.com/transport/current/pipelines#simulator-pipeline) to simulate poor network conditions to better determine how dropped unreliable RPC messages impacts your project.

com.unity.netcode.gameobjects/Documentation~/advanced-topics/network-update-loop-system/index.md

@@ -24,8 +24,8 @@ After injection, the player loops follows these stages. The player loop executes
 In all `NetworkUpdateStages`, it iterates over an array and calls the `NetworkUpdate` method over `INetworkUpdateSystem` interface, and the pattern is repeated.
 
 <Mermaid chart={`
-	graph LR;
-	A(Initialization)
+    graph LR;
+    A(Initialization)
     B(EarlyUpdate)
     C(FixedUpdate)
     D(PreUpdate)

com.unity.netcode.gameobjects/Documentation~/advanced-topics/network-update-loop-system/network-update-loop-reference.md

@@ -1,4 +1,4 @@
-# NetworkUpdateLoop reference 
+# NetworkUpdateLoop reference
 
 The following diagrams provide insight into the Network Update Loop process and APIs.
 

com.unity.netcode.gameobjects/Documentation~/advanced-topics/object-pooling.md

@@ -6,7 +6,7 @@ See [Introduction to Object Pooling](https://learn.unity.com/tutorial/introducti
 
 ## NetworkPrefabInstanceHandler
 
-You can register your own spawn handlers by including the `INetworkPrefabInstanceHandler` interface and registering with the `NetworkPrefabHandler`.  
+You can register your own spawn handlers by including the `INetworkPrefabInstanceHandler` interface and registering with the `NetworkPrefabHandler`.
 ```csharp
     public interface INetworkPrefabInstanceHandler
     {

com.unity.netcode.gameobjects/Documentation~/advanced-topics/ways-to-synchronize.md

@@ -16,7 +16,7 @@ The Netcode for GameObjects messaging system allows you to send and receive mess
 
 ### Remote procedure calls (RPCs)
 
-RPCs are a way of sending an event notification as well as a way of handling direct communication between a server and a client, or between clients and the [distributed authority service](../terms-concepts/distributed-authority.md). This is sometimes useful when the ownership scope of the `NetworkBehavior`, that the remote procedure call is declared within, belongs to the server but you still want one or more clients to be able to communicate with the associated NetworkObject.  
+RPCs are a way of sending an event notification as well as a way of handling direct communication between a server and a client, or between clients and the [distributed authority service](../terms-concepts/distributed-authority.md). This is sometimes useful when the ownership scope of the `NetworkBehavior`, that the remote procedure call is declared within, belongs to the server but you still want one or more clients to be able to communicate with the associated NetworkObject.
 
 Usage examples:
 

com.unity.netcode.gameobjects/Documentation~/basics/custom-networkvariables.md

@@ -164,7 +164,7 @@ This example shows a custom `NetworkVariable` type to help you understand how yo
         {
             // Do nothing for this example
         }
-    }    
+    }
 
     /// Bare minimum example of generic NetworkVariableBase derived class
     [Serializable]

com.unity.netcode.gameobjects/Documentation~/basics/deferred-despawning.md

@@ -155,7 +155,7 @@ public class ExplodingProjectile : NetworkBehaviour
                 m_SpawnedExplosion.SetParticlePlayingState(true);
             }
             m_ExplosionFx.OnValueChanged -= OnExplosionFxChanged;
-        }        
+        }
         base.OnNetworkDespawn();
     }
 }