| @@ -13,9 +13,9 @@ to stay in line with Discord internally. | |||||
| ## Implementation Specific Entities | ## Implementation Specific Entities | ||||
| Discord.Net is split into a core library and three different | |||||
| implementations - `Discord.Net.Core`, `Discord.Net.Rest`, | |||||
| `Discord.Net.Rpc`, and `Discord.Net.WebSockets`. | |||||
| Discord.Net is split into a core library and two different | |||||
| implementations - `Discord.Net.Core`, `Discord.Net.Rest`, and | |||||
| `Discord.Net.WebSockets`. | |||||
| As a bot developer, you will only need to use `Discord.Net.WebSockets`, | As a bot developer, you will only need to use `Discord.Net.WebSockets`, | ||||
| but you should be aware of the differences between them. | but you should be aware of the differences between them. | ||||
| @@ -30,10 +30,6 @@ addon will run on all platforms. | |||||
| **strictly** with the REST portion of Discord's API. Entities in this | **strictly** with the REST portion of Discord's API. Entities in this | ||||
| implementation are prefixed with `Rest` (e.g., `RestChannel`). | implementation are prefixed with `Rest` (e.g., `RestChannel`). | ||||
| `Discord.Net.Rpc` provides a set of concrete classes that are used | |||||
| with Discord's RPC API. Entities in this implementation are prefixed | |||||
| with `Rpc` (e.g., `RpcChannel`). | |||||
| `Discord.Net.WebSocket` provides a set of concrete classes that are | `Discord.Net.WebSocket` provides a set of concrete classes that are | ||||
| used primarily with Discord's WebSocket API or entities that are kept | used primarily with Discord's WebSocket API or entities that are kept | ||||
| in cache. When developing bots, you will be using this implementation. | in cache. When developing bots, you will be using this implementation. | ||||