Use 'import' instead of 'airdrop'

Author: patricijabrecko

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

@@ -39,13 +39,13 @@ A _sync unit_ is one self-encompassing unit of data that is synced to an externa
 - An organization Zendesk.
 
 In Jira, users often have multiple projects. Each project acts as an individual sync unit. 
-In contrast, Zendesk operates with a single large pool of tickets and agents. Here, the entire Zendesk instance can be synced in a single airdrop.
+In contrast, Zendesk operates with a single large pool of tickets and agents. Here, the entire Zendesk instance can be synced in a single import.
 
 ### Sync run
 
 Airdrop extractions are done in _sync runs_.
 A sync run is one end-to-end (extract-transform-load) execution of a _sync unit_.
-If you do an initial import from the external system to DevRev, that import will be one sync run.
+If you do an initial import from the external system to DevRev, that import is one sync run.
 Another import in the same direction is another sync run.
 And if you then decide to do a reverse sync from DevRev to the external system, that would be another
 sync run.

fern/docs/pages/airdrop/local-development.mdx

@@ -49,10 +49,10 @@ DevRev offers a starter Airdrop snap-in template that is ready for immediate use
 
 # Initial sync 
 
-Now that you have a running snap-in, you can start an airdrop.
+Now that you have a running snap-in, you can start an import.
 Go to DevRev app and click **Airdrops** -> **Start Airdrop** -> **Your snap-in**.
 
-1. Starting an airdrop begins with establishing a connection to the external system. The Airdrop snap-in prompts for specific information needed to create this connection. Afterwards, the snap-in verifies that the connection is successful and you should see a success message.
+1. Starting an import begins with establishing a connection to the external system. The Airdrop snap-in prompts for specific information needed to create this connection. Afterwards, the snap-in verifies that the connection is successful and you should see a success message.
 
 2. Once the connection is established, the snap-in collects information from the external system about the data unit to be exported. This phase is called _external sync units extraction_. An external sync unit is the data unit from the external system to be imported to DevRev. At this point, the DevRev app prompts the user to select an external sync unit from the list.
 
@@ -66,4 +66,4 @@ Go to DevRev app and click **Airdrops** -> **Start Airdrop** -> **Your snap-in**
 
 The process described above is called the **initial sync**. In all subsequent syncs, the first two steps are skipped.
 
-The snap-in constantly communicates with Airdrop platform, which manages its behavior. When an action occurs in the DevRev app, Airdrop platform sends a message to the snap-in with details about the event. The snap-in performs an action based on the event type. For example, when a user starts a new airdrop for the first time, Airdrop platform instructs the snap-in to perform an external sync unit extraction. The snap-in carries out the task and sends back available sync units to Airdrop platform.
+The snap-in constantly communicates with Airdrop platform, which manages its behavior. When an action occurs in the DevRev app, Airdrop platform sends a message to the snap-in with details about the event. The snap-in performs an action based on the event type. For example, when a user starts a new import for the first time, Airdrop platform instructs the snap-in to perform an external sync unit extraction. The snap-in carries out the task and sends back available sync units to Airdrop platform.