Fix a bunch of broken links in docs.

docs/connector-development/ux-handbook.md

@@ -2,7 +2,7 @@
 
 ## Connector Development UX Handbook
 
-![Connector UX Handbook](https://imgs.xkcd.com/comics/ui\_vs\_ux.png)
+![Connector UX Handbook](../.gitbook/assets/uivsux.png)
 
 ### Overview
 
@@ -53,7 +53,7 @@ The same is true with Airbyte: if it worked less than 99% of the time, many user
 
 Our users have the following hierarchy of needs: 
 
-![](../.gitbook/assets/ux\_hierarchy\_pyramid2.png)
+![](../.gitbook/assets/ux_hierarchy_pyramid2.png)
 
 **Security**
 
@@ -152,7 +152,7 @@ For example, the following spec:
 
 produces the following input field in the UI: 
 
-![](../.gitbook/assets/ux\_username\_bad.png)
+![](../.gitbook/assets/ux_username_bad.png)
 
 Whereas the following specification:
 
@@ -171,7 +171,7 @@ Whereas the following specification:
 
 produces the following UI:
 
-![](../.gitbook/assets/ux\_username\_good.png)
+![](../.gitbook/assets/ux_username_good.png)
 
 The title should use Pascal Case “with spaces” e.g: “Attribution Lookback Window”, “Host URL”, etc...
 

docs/integrations/sources/amazon-sqs.md

@@ -35,7 +35,7 @@ The stream record data will have three fields:
 Required properties are 'Queue URL', 'AWS Region' and 'Delete Messages After Read' as noted in **bold** below.
 
 * **Queue URL** (STRING)
-  * The full AWS endpoint URL of the queue e.g. https://sqs.eu-west-1.amazonaws.com/1234567890/example-queue-url
+  * The full AWS endpoint URL of the queue e.g. `https://sqs.eu-west-1.amazonaws.com/1234567890/example-queue-url`
 * **AWS Region** (STRING)
   * The region code for the SQS Queue e.g. eu-west-1
 * **Delete Messages After Read** (BOOLEAN)

docs/integrations/sources/lemlist.md

@@ -10,10 +10,10 @@ This source can sync data for the [Lemlist API](https://developer.lemlist.com/#i
 
 This Source is capable of syncing the following core Streams:
 
-* [Team](https://api.lemlist.com/api/team)
-* [Campaigns](https://api.lemlist.com/api/campaigns)
-* [Activities](chttps://api.lemlist.com/api/activities)
-* [Unsubscribes](https://api.lemlist.com/api/unsubscribes)
+* [Team](`api.lemlist.com/api/team`)
+* [Campaigns](`api.lemlist.com/api/campaigns`)
+* [Activities](`api.lemlist.com/api/activities`)
+* [Unsubscribes](`api.lemlist.com/api/unsubscribes`)
 
 ### Features
 

docs/integrations/sources/recharge.md

@@ -44,7 +44,7 @@ The Recharge connector should gracefully handle Recharge API limitations under n
 
 ### Setup guide
 
-Please read [How to generate your API token](https://support.rechargepayments.com/hc/en-us/articles/360008829993-ReCharge-API-).
+Please read [How to generate your API token](https://support.rechargepayments.com/hc/en-us/articles/360008829993-ReCharge-API).
 
 ## Changelog
 

docs/integrations/sources/twilio.md

@@ -43,7 +43,7 @@ Several output streams are available from this source:
 
 ### Performance considerations
 
-The Twilio connector will gracefully handle rate limits. For more information, see [the Twilio docs for rate limitations](https://support.twilio.com/hc/en-us/articles/360044308153-Twilio-API-response-Error-429-Too-Many-Requests-).
+The Twilio connector will gracefully handle rate limits. For more information, see [the Twilio docs for rate limitations](https://support.twilio.com/hc/en-us/articles/360044308153-Twilio-API-response-Error-429-Too-Many-Requests).
 
 Get in touch with [Twilio Sales](https://twilio.com/help/sales) to talk to them about your use case and request an increased concurrency limit.
 

docs/understanding-airbyte/glossary.md

@@ -10,7 +10,7 @@ DAG stands for **Directed Acyclic Graph**. It's a term originally coined by math
 
  
 
-![](../.gitbook/assets/glossary\_dag\_example.png)
+![](../.gitbook/assets/glossary_dag_example.png)
 
 ### ETL/ELT