fix: dead links on docs.revert.dev (#466)

Author: ashutosh-revert

fern/docs/contents/developer-guides.mdx

@@ -1,19 +1,19 @@
 # Requirements
+
 ## System Requirements
 
 Before you start, make sure you have the following applications and their minimum versions installed, in addition to Node.js and yarn (as mentioned earlier):
 
-- **Node.js 18.0.0** or later
-- **Yarn 3.0.2** or later
-- macOS, Windows (including WSL), and Linux are supported.
+-   **Node.js 18.0.0** or later
+-   **Yarn 3.0.2** or later
+-   macOS, Windows (including WSL), and Linux are supported.
 
 ## System Requirements
 
 ## Get Started
 
 ### setup
 
-
 1 . Clone the forked repository and open the created directory
 
 ```shell
@@ -24,7 +24,7 @@ cd revert
 
 2 . Install dependencies
 
-```shell 
+```shell
 yarn
 ```
 
@@ -58,10 +58,12 @@ yarn workspace @revertdotdev/backend db-seed
 
 ### Running the API locally
 
--   Run 
-```shell 
-yarn workspace @revertdotdev/backend dev 
-``` 
+-   Run
+
+```shell
+yarn workspace @revertdotdev/backend dev
+```
+
 to the run service locally at `:4001`
 
 4 . client setup
@@ -77,38 +79,31 @@ cp packages/client/.env.example packages/client/.env
 
 1. Generate a Tunnel URL
 
-- First, generate a tunnel URL using `ngrok http <4001 or YOUR_SERVER_PORT>`
-- Copy this URL to your clipboard as you'll need it in the next steps.
+-   First, generate a tunnel URL using `ngrok http <4001 or YOUR_SERVER_PORT>`
+-   Copy this URL to your clipboard as you'll need it in the next steps.
 
 2. Configure Clerk Webhook Endpoint
 
-- Access your Clerk dashboard (Sign up on https://clerk.com/ if you have note already).
-- Navigate to the webhook settings or configuration section.
-- Ensure that the webhook endpoint is set to `<YOUR_LOCALHOST_OR_PUBLIC_URL>/clerk/webhook`
-- Ensure that you are listening to the `user.created` event by ticking the `user`object under `Message Filtering`
-
-
-
-<img
-src="https://res.cloudinary.com/dfcnic8wq/image/upload/v1702896296/Revert/Docs/ioj7i0dj97dzcmgb95p2.png"
-/>
-
+-   Access your Clerk dashboard (Sign up on https://clerk.com/ if you have note already).
+-   Navigate to the webhook settings or configuration section.
+-   Ensure that the webhook endpoint is set to `<YOUR_LOCALHOST_OR_PUBLIC_URL>/clerk/webhook`
+-   Ensure that you are listening to the `user.created` event by ticking the `user`object under `Message Filtering`
 
+<img src="https://res.cloudinary.com/dfcnic8wq/image/upload/v1702896296/Revert/Docs/ioj7i0dj97dzcmgb95p2.png" />
 
 3. Sign Up in Your Application
 
- - Use your application to sign up a new user. This action will trigger a user creation event.
- - In your Clerk dashboard, you should now see a `user.created` object associated with the newly signed-up user.
+-   Use your application to sign up a new user. This action will trigger a user creation event.
+-   In your Clerk dashboard, you should now see a `user.created` object associated with the newly signed-up user.
 
 4. Testing with Postman
 
- - To verify that Clerk is sending user creation notifications to your endpoint, you can use Postman for testing.
-
- - Open Postman and create a new request.
+-   To verify that Clerk is sending user creation notifications to your endpoint, you can use Postman for testing.
 
- - Set the HTTP method to POST.
+-   Open Postman and create a new request.
 
- - In the request's URL field, use http://localhost:4001/clerk/webhook. This is the endpoint Clerk will send webhook events to.
+-   Set the HTTP method to POST.
 
- - In the request body, paste the `user.created` object that you copied from your Clerk dashboard.
+-   In the request's URL field, use `http://localhost:4001/clerk/webhook`. This is the endpoint Clerk will send webhook events to.
 
+-   In the request body, paste the `user.created` object that you copied from your Clerk dashboard.

fern/docs/contents/docker-compose.mdx

@@ -29,28 +29,26 @@ docker-compose up -d
 
 ```
 
-The UI is now available at http://localhost:3000 and the backend is available at http://localhost:4001. This also contains a Postgres database alongside the API. 
-
+The UI is now available at `http://localhost:3000` and the backend is available at `http://localhost:4001`. This also contains a Postgres database alongside the API.
 
 #### Run Revert with your own database & redis
 
-The above steps allow you to spin up a Postgres & Redis instance alongside the API and UI. 
-
-To use your own Postgres & Redis instance run the following set of commands: 
+The above steps allow you to spin up a Postgres & Redis instance alongside the API and UI.
 
+To use your own Postgres & Redis instance run the following set of commands:
 
 ```shell
 
 # Seed the database
 
-docker run \ 
+docker run \
     -e PGSQL_URL=postgresql://<PG_USER>:<PG_PASSWORD>@<PG_HOST>:<PG_PORT>/<PG_DB> \
     docker.revert.dev/revertengg/revert-db-seed:latest
 
 # To run Revert API:
 
 docker run \
-  -v cache:/data \ 
+  -v cache:/data \
   -v pgdata:/var/lib/postgresql/data \
   -e PGSQL_URL=postgresql://<PG_USER>:<PG_PASSWORD>@<PG_HOST>:<PG_PORT>/<PG_DB> \
   -e REDIS_SERVER_URL=redis://<REDIS_USER>:<REDIS_PASSWORD>@<REDIS_HOST>:<REDIS_PORT> \

fern/docs/contents/usecases.mdx

@@ -23,5 +23,5 @@ Here are a few business use cases Revert APIs solve for with the suite of unifie
     Push the results back to the CRM as custom fields and objects, boosting your revenue intelligence and ensuring a seamless data flow.
 
 <Cards center>
-    <Card title="Check CRMs supported" href="/overview/crm-support" />
+    <Card title="Check CRMs supported" href="/overview/api-integrations-support/cr-ms" />
 </Cards>