fix: Minor Airdrop fixes (#200)

* Minor Airdrop fixes

* Fix links to airdrop template

Author: patricijabrecko

fern/docs/pages/airdrop/attachments-extraction.mdx

@@ -31,7 +31,7 @@ type `EXTRACTION_ATTACHMENTS_ERROR`.
 ## Implementation
 
 Attachments extraction is already provided by SDK, but if you need to customize it for your use case,
-it should be implemented in the [attachments-extraction.ts](https://github.com/devrev/adaas-template/blob/main/code/src/functions/extraction/workers/attachments-extraction.ts) file.
+it should be implemented in the [attachments-extraction.ts](https://github.com/devrev/airdrop-template/blob/main/code/src/functions/extraction/workers/attachments-extraction.ts) file.
 
 After uploading an attachment or a batch of attachments, the extractor also has to prepare and
 upload a file specifying the extracted and uploaded attachments.

fern/docs/pages/airdrop/data-extraction.mdx

@@ -34,7 +34,7 @@ message with event of type `EXTRACTION_DATA_ERROR`.
 
 ## Implementation
 
-Data extraction should be implemented in the [data-extraction.ts](https://github.com/devrev/adaas-template/blob/main/code/src/functions/extraction/workers/data-extraction.ts) file.
+Data extraction should be implemented in the [data-extraction.ts](https://github.com/devrev/airdrop-template/blob/main/code/src/functions/extraction/workers/data-extraction.ts) file.
 
 During the data extraction phase, the snap-in uploads batches of extracted items (with tooling from `@devrev/adaas-sdk`).
 
@@ -103,7 +103,7 @@ A snap-in must consult its state to obtain information on when the last successf
 
 Effective use of the state and breaking down the problem into smaller chunks are crucial for good performance and user experience. Without knowing what has been processed, the snap-in extracts the same data multiple times, using valuable API capacity and time, and possibly duplicates the data inside DevRev or the external application.
 
-The snap-in starter template contains an [example](https://github.com/devrev/adaas-template/blob/main/code/src/functions/extraction/index.ts) of a simple state. Adding more data to the state can help with pagination and rate limiting by saving the point at which extraction was left off.
+The snap-in starter template contains an [example](https://github.com/devrev/airdrop-template/blob/main/code/src/functions/extraction/index.ts) of a simple state. Adding more data to the state can help with pagination and rate limiting by saving the point at which extraction was left off.
 
 To test the state in development, you can decrease the timeout between snap-in invocations.
 

fern/docs/pages/airdrop/external-sync-units-extraction.mdx

@@ -11,7 +11,7 @@ External sync unit extraction is executed only during the initial import.
 
 ### Implementation
 
-This phase should be implemented in the [`external-sync-units-extraction.ts`](https://github.com/devrev/adaas-template/blob/main/code/src/functions/extraction/workers/external-sync-units-extraction.ts) file.
+This phase should be implemented in the [`external-sync-units-extraction.ts`](https://github.com/devrev/airdrop-template/blob/main/code/src/functions/extraction/workers/external-sync-units-extraction.ts) file.
 
 The snap-in should emit the list of external sync units in the given format:
 

fern/docs/pages/airdrop/getting-started.mdx

@@ -35,9 +35,9 @@ consider gathering the following information:
 ### Sync unit
 
 A _sync unit_ is one self encompassing unit of data that is synced to an external system. Examples:
-- Jira project
-- SalesForce
-- Zendesk
+- A project in Jira.
+- An account in SalesForce.
+- An organization Zendesk.
 
 ### Sync run
 

fern/docs/pages/airdrop/manifest.mdx

@@ -57,7 +57,7 @@ They are called **Connections** in the DevRev app.
 
 ### Configure a keyring
 
-Keyrings are configured in the `manifest.yaml` by configuring a `keyring_type`, like in the [example](https://github.com/devrev/adaas-template/blob/main/manifest.yaml).
+Keyrings are configured in the `manifest.yaml` by configuring a `keyring_type`, like in the [example](https://github.com/devrev/airdrop-template/blob/main/manifest.yaml).
 
 ```yaml
 keyring_types:

fern/docs/pages/airdrop/metadata-extraction.mdx

@@ -3,7 +3,7 @@ During the metadata extraction phase, the snap-in must provide an
 This file provides a structured way of describing the external system's domain model,
 including its domain entities, types, relationships, and other metadata.
 
-You can check which object types for Airdrop DevRev supports [here](/snapin-development/airdrop/supported-object-types).
+You can check which object types for Airdrop DevRev supports [here](/public/snapin-development/adaas/supported-object-types).
 
 ## Triggering event
 
@@ -15,7 +15,7 @@ when done, or `EXTRACTION_METADATA_ERROR` in case of an error.
 
 ## Implementation
 
-Metadata extraction should be implemented in the [metadata-extraction.ts](https://github.com/devrev/adaas-template/blob/main/code/src/functions/extraction/workers/metadata-extraction.ts) file.
+Metadata extraction should be implemented in the [metadata-extraction.ts](https://github.com/devrev/airdrop-template/blob/main/code/src/functions/extraction/workers/metadata-extraction.ts) file.
 
 ```typescript
 import { ExtractorEventType, processTask } from "@devrev/ts-adaas";

fern/docs/pages/airdrop/overview.mdx

@@ -6,6 +6,6 @@ DevRev provides a range of snap-ins available through the DevRev marketplace for
 various external systems like Jira and Zendesk. Sometimes, a specific snap-in may not be available
 for a given external system. This is why DevRev enables creation of external connectors (extractors
 and loaders) to other developers, allowing them to integrate with DevRev’s Airdrop and develop their 
-Airdrop own snap-ins.
+own Airdrop snap-ins.
 
 You can learn more about Airdrop in the [general documentation](https://docs.devrev.ai/import#airdrop-features).

fern/docs/pages/airdrop/snap-in-examples.mdx

@@ -1,5 +1,5 @@
-You can find snap-in examples for various external systems [here](https://github.com/devrev/adaas-connector-examples).
+You can find snap-in examples for various external systems [here](https://github.com/devrev/airdrop-examples).
 
-Examples include:
+Examples currently include:
 
 - Asana

fern/docs/pages/airdrop/snap-in-template.mdx

@@ -1,4 +1,4 @@
-Airdrop snap-in starter template is available [here](https://github.com/devrev/adaas-template).
+Airdrop snap-in starter template is available [here](https://github.com/devrev/airdrop-template).
 
 The template makes use of **[DevRev's SDK library](https://www.npmjs.com/package/@devrev/ts-adaas)**,
 which helps developers build snap-ins that integrate with DevRev’s Airdrop platform. 
@@ -18,7 +18,7 @@ It provides features such as:
 
 If you check the template, you can see that a snap-in is a Node.js project with a specific file structure:
 
-```
+```yaml
 - manifest.yaml
 - code/
   - scripts/