Docs: Update broken links (airbytehq#23940)

* updated_links_in_docs

* updated more links

* typo

* removed backticks

* deleted links in deploying on cloud and local deployment

Author: sophia-wiley

docs/archive/changelog/platform.md

@@ -331,7 +331,7 @@ This interim patch period mostly contained stability changes for Airbyte Cloud,
 * Normalization now supports union data types
 * Support longform text inputs in the UI for cases where you need to preserve formatting on connector inputs like .pem keys
 * Expose the latest available connector versions in the API
-* Airflow: published a new [tutorial](https://docs.airbyte.com/tutorials/using-the-airflow-airbyte-operator) for how to use the Airbyte operator. Thanks [@Marcos Marx](https://github.com/marcosmarxm) for writing the tutorial! 
+* Airflow: published a new [tutorial](https://docs.airbyte.com/operator-guides/using-the-airflow-airbyte-operator/) for how to use the Airbyte operator. Thanks [@Marcos Marx](https://github.com/marcosmarxm) for writing the tutorial! 
 * Connector Contributions: All connectors now describe how to contribute to them without having to touch Airbyte’s monorepo build system -- just work on the connector in your favorite dev setup!
 
 ## [03-08-2021 - 0.17](https://github.com/airbytehq/airbyte/releases/tag/v0.17.0-alpha)

docs/archive/examples/postgres-replication.md

@@ -30,7 +30,7 @@ You should see an onboarding page. Enter your email and continue.
 
 ## 2. Set up your first connection
 
-We support a growing [list of source connectors](../../category/sources). For now, we will start out with a Postgres source and destination.
+We support a growing [list of source connectors](https://docs.airbyte.com/category/sources). For now, we will start out with a Postgres source and destination.
 
 **If you don't have a readily available Postgres database to sync, here are some quick instructions:**  
 Run the following commands in a new terminal window to start backgrounded source and destination databases:

docs/connector-development/debugging-docker.md

@@ -4,7 +4,7 @@ worker container, such as a Destination container. This guide will assume use of
 however the steps could be applied to another IDE or debugger.
 
 ## Prerequisites
-You should have the airbyte repo downloaded and should be able to [run the platform locally](/deploying-airbyte/local-deployment).
+You should have the airbyte repo downloaded and should be able to [run the platform locally](https://docs.airbyte.com/deploying-airbyte/local-deployment).
 Also, if you're on macOS you will need to follow the installation steps for [Docker Mac Connect](https://github.com/chipmk/docker-mac-net-connect).
 
 ## Connecting your debugger

docs/deploying-airbyte/local-deployment.md

@@ -22,7 +22,7 @@ cd airbyte
 ```
 
 - In your browser, just visit [http://localhost:8000](http://localhost:8000)
-- You will be asked for a username and password. By default, that's username `airbyte` and password `password`. Once you deploy airbyte to your servers, be sure to [change these](/operator-guides/security):
+- You will be asked for a username and password. By default, that's username `airbyte` and password `password`. Once you deploy Airbyte to your servers, be sure to change these:
 
 ```yaml
 # Proxy Configuration
@@ -62,7 +62,7 @@ bash run-ab-platform.sh
 ```
 
 - In your browser, just visit [http://localhost:8000](http://localhost:8000)
-- You will be asked for a username and password. By default, that's username `airbyte` and password `password`. Once you deploy airbyte to your servers, be sure to [change these](/operator-guides/security).
+- You will be asked for a username and password. By default, that's username `airbyte` and password `password`. Once you deploy airbyte to your servers, be sure to change these.
 - Start moving some data!
 
 ## Troubleshooting

docs/deploying-airbyte/on-cloud.md

@@ -8,8 +8,6 @@ Airbyte Cloud requires no setup and can be immediately run from your web browser
 
 **1. Using the Airbyte Cloud invite link provided to you, click `Sign up`, and verify your email.**
 
-If you don't have an invite, sign up [here!](https://airbyte.com/cloud-waitlist)
-
 **2. Click on the default workspace.**
 
 You will be provided 1000 credits to get your first few syncs going!

docs/deploying-airbyte/on-kubernetes.md

@@ -1,7 +1,7 @@
 # (Deprecated) Deploy Airbyte on Kubernetes using Kustomize
 
 :::caution
-This deployment method uses Kustomize and is only supported up to [Airbyte version `0.40.32`](https://github.com/airbytehq/airbyte/releases/tag/v0.40.32). For existing deployments, check out [commit `21a7e102183e20d2d4998ea70c2a8fe4eac8921b`](https://github.com/airbytehq/airbyte/commit/21a7e102183e20d2d4998ea70c2a8fe4eac8921b) to continue deploying using Kustomize. For new deployments, [deploy Airbyte on Kubernetes via Helm](/deploying-airbyte/on-kubernetes-via-helm.md).
+This deployment method uses Kustomize and is only supported up to [Airbyte version `0.40.32`](https://github.com/airbytehq/airbyte/releases/tag/v0.40.32). For existing deployments, check out [commit `21a7e102183e20d2d4998ea70c2a8fe4eac8921b`](https://github.com/airbytehq/airbyte/commit/21a7e102183e20d2d4998ea70c2a8fe4eac8921b) to continue deploying using Kustomize. For new deployments, [deploy Airbyte on Kubernetes via Helm](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm).
 :::
 
 This page guides you through deploying Airbyte Open Source on Kubernetes. 

docs/integrations/destinations/amazon-sqs.md

@@ -40,7 +40,7 @@ If the target SQS Queue is not public, you will need the following permissions o
 Required properties are 'Queue URL' and 'AWS Region' 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
 * Message Delay (INT)
@@ -107,4 +107,4 @@ The output SQS message would contain:
 
 | Version | Date | Pull Request | Subject |
 | :--- | :--- | :--- | :--- |
-| `0.1.0` | 2021-10-27 | [\#0000](https://github.com/airbytehq/airbyte/pull/0000) | `Initial version` |
+| `0.1.0` | 2021-10-27 | [\#0000](https://github.com/airbytehq/airbyte/pull/0000) | `Initial version` |

docs/integrations/destinations/bigquery-denormalized.md

@@ -1,6 +1,6 @@
 # Bigquery Denormalized
 
-See [destinations/bigquery](/integrations/destinations/bigquery)
+See [destinations/bigquery](https://docs.airbyte.com/integrations/destinations/bigquery)
 
 ## Changelog
 

docs/integrations/destinations/chargify.md

@@ -57,7 +57,7 @@ The Chargify Connector requires your `Project ID` and `Master Key` for authentic
 
 #### Timestamp Inference
 
-The `Infer Timestamp` field lets you specify if you want the connector to infer the [chargify.timestamp](https://help.chargify.com/events/getting-data-in-guide.html#event-timestamps) field based on the data from the event that occurred in the source application. This feature allows for historical data synchronization enabling you to fully leverage the power of Chargify's time series analytics. By default, this property is set to true. If toggled off, chargify.timestamp will be set to the datetime when the data was recorded by Chargify.
+The `Infer Timestamp` field lets you specify if you want the connector to infer the [chargify.timestamp](https://maxio-chargify.zendesk.com/hc/en-us/articles/5405362457613#event-timestamps) field based on the data from the event that occurred in the source application. This feature allows for historical data synchronization enabling you to fully leverage the power of Chargify's time series analytics. By default, this property is set to true. If toggled off, chargify.timestamp will be set to the datetime when the data was recorded by Chargify.
 
 ### Setup the Chargify destination in Airbyte
 

docs/integrations/destinations/r2.md

@@ -271,7 +271,7 @@ The following configuration is available to configure the Parquet output:
 | `dictionary_page_size_kb` | integer | 1024 \(KB\) | **Dictionary Page Size** in KB. There is one dictionary page per column per row group when dictionary encoding is used. The dictionary page size works like the page size but for dictionary. |
 | `dictionary_encoding` | boolean | `true` | **Dictionary encoding**. This parameter controls whether dictionary encoding is turned on. |
 
-These parameters are related to the `ParquetOutputFormat`. See the [Java doc](https://www.javadoc.io/doc/org.apache.parquet/parquet-hadoop/1.12.0/org/apache/parquet/hadoop/ParquetOutputFormat.html) for more details. Also see [Parquet documentation](https://parquet.apache.org/documentation/latest/#configurations) for their recommended configurations \(512 - 1024 MB block size, 8 KB page size\).
+These parameters are related to the `ParquetOutputFormat`. See the [Java doc](https://www.javadoc.io/doc/org.apache.parquet/parquet-hadoop/1.12.0/org/apache/parquet/hadoop/ParquetOutputFormat.html) for more details. Also see [Parquet documentation](https://parquet.apache.org/docs/file-format/configurations/) for their recommended configurations \(512 - 1024 MB block size, 8 KB page size\).
 
 #### Data schema