Proofread and improve the whole class reference

- Document a few more properties and methods
- Add more information to many classes
- Fix lots of typos and gramar mistakes
- Use [code] tags for parameters consistently
- Use [b] and [i] tags consistently
- Put "Warning:" and "Note:" on their own line to be more visible,
  and make them always bold
- Tweak formatting in code examples to be more readable
- Use double quotes consistently
- Add more links to third-party technologies

modules/websocket/doc_classes/WebSocketMultiplayerPeer.xml

@@ -30,10 +30,10 @@
 			<argument index="3" name="output_max_packets" type="int">
 			</argument>
 			<description>
-				Configure the buffers sizes for this WebSocket peer. Default values can be specified in project settings under [code]network/limits[/code]. For server, values are meant per connected peer.
+				Configures the buffer sizes for this WebSocket peer. Default values can be specified in the Project Settings under [code]network/limits[/code]. For server, values are meant per connected peer.
 				The first two parameters define the size and queued packets limits of the input buffer, the last two of the output buffer.
 				Buffer sizes are expressed in KiB, so [code]4 = 2^12 = 4096 bytes[/code]. All parameters will be rounded up to the nearest power of two.
-				NOTE: HTML5 exports only use the input buffer since the output one is managed by browsers.
+				[b]Note:[/b] HTML5 exports only use the input buffer since the output one is managed by browsers.
 			</description>
 		</method>
 	</methods>
@@ -42,7 +42,8 @@
 			<argument index="0" name="peer_source" type="int">
 			</argument>
 			<description>
-				Emitted when a packet is received from a peer. Note: this signal is only emitted when the client or server is configured to use Godot multiplayer API.
+				Emitted when a packet is received from a peer.
+				[b]Note:[/b] This signal is only emitted when the client or server is configured to use Godot multiplayer API.
 			</description>
 		</signal>
 	</signals>