diff --git a/docs/guides/getting_started/terminology.md b/docs/guides/getting_started/terminology.md
index 0f24edd6f..d99c4526a 100644
--- a/docs/guides/getting_started/terminology.md
+++ b/docs/guides/getting_started/terminology.md
@@ -15,11 +15,15 @@ to stay in line with Discord internally.
 
 Discord.Net is split into a core library and two different
 implementations - `Discord.Net.Core`, `Discord.Net.Rest`, and
-`Discord.Net.WebSockets`.
+`Discord.Net.WebSocket`.
 
-As a bot developer, you will only need to use `Discord.Net.WebSockets`,
+As a common bot developer, you will only need to use `Discord.Net.WebSocket`,
 but you should be aware of the differences between them.
 
+> [!TIP]
+> If you are looking to implement Rest based interactions, or handle calls over REST in any other way,
+> `Discord.Net.Rest` is the resource most applicable to you. 
+
 `Discord.Net.Core` provides a set of interfaces that models Discord's
 API. These interfaces are consistent throughout all implementations of
 Discord.Net, and if you are writing an implementation-agnostic library
@@ -33,4 +37,4 @@ implementation are prefixed with `Rest` (e.g., `RestChannel`).
 `Discord.Net.WebSocket` provides a set of concrete classes that are
 used primarily with Discord's WebSocket API or entities that are kept
 in cache. When developing bots, you will be using this implementation.
-All entities are prefixed with `Socket` (e.g., `SocketChannel`).
\ No newline at end of file
+All entities are prefixed with `Socket` (e.g., `SocketChannel`).