chore: squash

docs/clients/enabling-a-client.mdx

@@ -14,11 +14,11 @@ import TOCInline from '@theme/TOCInline';
 Before we can start interacting with a provider, we need ask the provider to enable the client. This will achieve two things:
 
 * if necessary, it will authorize your client with the provider; and
-* it will get a list of the authorized accounts available for your client to use.
+* it will get a list of the authorized accounts available to your client.
 
 :::note
 
-It should be safe to call [`enable()`](../../api-reference/avm-web-client#enable) as many times as your client wants, the provider should assume this.
+It should be safe to call [`enable()`](../../api-reference/avm-web-client#enable) as many times as your client needs; the provider should assume this.
 
 :::
 

docs/providers/responding-to-enable-requests.mdx

@@ -11,7 +11,7 @@ import TOCInline from '@theme/TOCInline';
 
 ## Overview
 
-The main purpose of an enable request to is for clients to get a list of authorized accounts. However, it can be used to handle sessioning. While it is not enforced through this SDk, it is heavily recommended.
+The main purpose of an enable request to is for clients to get a list of authorized accounts. However, it can be used to handle sessioning. While it is not enforced through this SDK, it is heavily recommended.
 
 ## Responding to an anonymous request
 

docs/scripts/sidebars.js

@@ -4,6 +4,7 @@
 const sidebars = {
   docs: [
     'overview',
+    'terminology',
     {
       items: [
         'clients/getting-started',
@@ -30,7 +31,6 @@ const sidebars = {
       },
       type: 'category',
     },
-    'terminology',
     {
       items: [
         'api-reference/avm-web-client',