Small calarification in connecting docs.

Author: FiniteSingularity

docs/api/connecting.md

@@ -11,15 +11,15 @@ A TAU token is required for both the realtime websocket API and the REST API.  T
 TAU exposes a websocket endpoint at `ws://localhost:PORT/ws/twitch-events/` for a local deployment or `wss://yourdomain:PORT/ws/twitch-events/` for a served deployment.  After connecting your client to the websocket, you must send a message containing the following json object:
 ```
 { 
-    "token": "YOUR TOKEN HERE"
+    "token": "YOUR TAU TOKEN HERE"
 }
 ```
 After receiving your token, TAU will begin to broadcast incoming twitch events to your client.
 
 ## Connecting to the REST API
 TAU also provides 2 separate REST APIs.  A passthrough of the Twitch Helix API at: `/api/twitch/helix`, and access to the data captured and stored by TAU at `/api/v1`.  In order to authenticate requests, you must include an Authorization header:
 ```
-Authorization: Token YOUR-TOKEN-HERE
+Authorization: Token YOUR-TAU-TOKEN-HERE
 ```
 The Update Token Scopes page from the dashboard will allow you to add scopes to the Twitch token used by TAU.
 
@@ -30,7 +30,7 @@ After connecting your client to the websocket, you must send a message containin
 
 ```
 { 
-    "token": "YOUR TOKEN HERE"
+    "token": "YOUR TAU TOKEN HERE"
 }
 ```
 

scripts/scrape_event_sub_docs.py

@@ -46,7 +46,7 @@ def get_type_dict(soup, id):
                 'description': cols[2].text.strip(),
                 'type': cols[1].text.strip(),
             }
-        
+
     return data