Apply suggestions from code review

Co-authored-by: Michael Beemer <beeme1mr@users.noreply.github.com>
Signed-off-by: Todd Baert <toddbaert@gmail.com>

specification/glossary.md

@@ -178,11 +178,11 @@ Server-side use cases typically perform flag evaluations on behalf of many users
 
 ### Single-Context Paradigm
 
-In contrast to server-side or other service-type applications, client side applications typically operate in the context of a single user. Most feature flagging libraries for these applications have been designed with this in mind. Frequently, Client/web libraries operate similarly to this:
+Client-side applications typically operate in the context of a single user. Most feature flagging libraries for these applications have been designed with this in mind. Frequently, Client/web libraries operate similarly to this:
 
 - an initialization occurs, which fetches evaluated flags in bulk for a given context (user)
 - the evaluated flags are cached in the library
 - flag evaluations take place against this cache, without a need to provide context (context was already used to evaluate flags in bulk)
 - functions are exposed on the libraries that signal the cache is no longer valid, and must be reconciled based on a context change, frequently involving a network request or I/O operation
 
-Not all client libraries work this way, but generally, libraries that accept dynamic context per evaluation can build providers which conform to this model with relative ease, while the reverse is not true.
+Not all client libraries work this way, but generally, libraries that accept dynamic context per evaluation can build [providers](#provider) which conform to this model with relative ease, while the reverse is not true.