Modify titles to sentence case.

Author: samod

fern/docs/pages/adaas/creating-a-keyring.mdx

@@ -1,4 +1,4 @@
-# Attachment Extraction phase
+# Attachments extraction phase
 
 For the Attachment Extraction phase of the import process,
 the Extractor has to upload each attachment to DevRev’s S3 using the `S3Interact` API. 

fern/docs/pages/adaas/extracting-attachments.mdx

@@ -1,4 +1,4 @@
-# Data Extraction Phase
+# Data extraction phase
 
 In the data extraction phase, the Extractor is expected to call the External System’s APIs
 to retrieve all the items that were updated since the start of the last extraction.

fern/docs/pages/adaas/extracting-data.mdx

@@ -1,4 +1,4 @@
-# Extract External Sync Units Phase
+# Extract external sync units phase
 
 In the External Sync Unit extraction phase, the Extractor is expected to get the list of projects, repositories, etc.
 (whatever the equivalent of those is called in the External System)

fern/docs/pages/adaas/extracting-external-sync-units.mdx

@@ -1,4 +1,4 @@
-# Extract Metadata Phase
+# Extract metadata phase
 
 During the `EXTRACT_METADATA` phase, the Worker must provide a JSON file named `initial_domain_mapping.json`,
 and upload it as an Artifact with item type `initial_domain_mapping`.

fern/docs/pages/adaas/extracting-metadata.mdx

@@ -1,4 +1,4 @@
-# Extraction Phases
+# Extraction phases
 
 Airdrop extractions are done in phases.
 Phases follow sequentially, and each can consist of one or more invocations of the Worker.
@@ -79,7 +79,7 @@ A Deletion Sync consists of the following phases:
 - Delete data,
 - Delete attachments.
 
-## External Sync Unit Extraction
+## External sync unit extraction
 
 External Sync Unit Extraction is an extraction phase, executed only during the Initial Import.
 It extracts External Sync Units available in the External System,
@@ -91,7 +91,7 @@ Airdrop initiates the External Sync Unit Extraction phase by starting the Worker
 The Worker must respond to Airdrop with a message with eventType `EXTRACTION_EXTERNAL_SYNC_UNITS_DONE`
 with a list of External Sync Units as a payload, or `EXTRACTION_EXTERNAL_SYNC_UNITS_ERROR` in case of an error.
 
-## Metadata Extraction
+## Metadata extraction
 
 Airdrop initiates the Metadata Extraction by starting the Worker with a message with eventType: `EXTRACTION_METADATA_START`.
 
@@ -102,7 +102,7 @@ to prepare and upload the Initial Domain Mapping to DevRev.
 The Worker must respond to Airdrop with a message with eventType `EXTRACTION_METADATA_DONE` when done,
 or `EXTRACTION_METADATA_ERROR` in case of an error.
 
-## Data Extraction
+## Data extraction
 
 Airdrop initiates Data Extraction by starting the Worker with a message with eventType `EXTRACTION_DATA_START`
 when transitioning to the Data Extraction phase.
@@ -124,7 +124,7 @@ Once the Data Extraction is done, the Worker must respond to Airdrop with a mess
 
 If Data Extraction failed in any moment of extraction, the Worker must respond to Airdrop with a message with eventType `EXTRACTION_DATA_ERROR`.
 
-## Attachments Extraction
+## Attachments extraction
 
 Airdrop initiates the Attachment Extraction by starting the Worker with a message with eventType `EXTRACTION_ATTACHMENTS_START`
 when transitioning to the Data Extraction phase.
@@ -146,7 +146,7 @@ Once the Attachment Extraction phase is done, the Worker must respond to Airdrop
 
 If Attachment Extraction failed, the Worker must respond to Airdrop with a message with eventType `EXTRACTION_ATTACHMENTS_ERROR`.
 
-## Delete Data
+## Delete data
 
 Airdrop initiates the Data Delete phase when the Sync is deleted from DevRev.
 It is started by sending the Worker a message with eventType: `EXTRACTION_DATA_DELETE`.
@@ -156,7 +156,7 @@ In the most common extraction use cases, there is nothing to do and Workers may
 
 The Worker must respond to Airdrop with a message with eventType `EXTRACTION_DATA_DELETE_DONE` when done or `EXTRACTION_DATA_DELETE_ERROR` in case of an error.
 
-## Delete Attachments
+## Delete attachments
 
 Airdrop initiates the Attachments Delete phase when the Sync is deleted from DevRev.
 It is started by sending the Worker a message with eventType: `EXTRACTION_ATTACHMENTS_DELETE`.

fern/docs/pages/adaas/extraction-phases.mdx

@@ -1,4 +1,4 @@
-# Getting Stated
+# Getting started
 
 1. Create a new repo from the ADaaS Template repo:
 On [https://github.com/devrev/adaas-template](https://github.com/devrev/adaas-template) use the dropdown button `Use this template` and
@@ -17,3 +17,25 @@ See [Creating a Keyring](https://www.notion.so/Creating-a-Keyring-aa497671dc1b42
 7. Install the Snap-In in your DevRev DevOrg on the web by navigating to `Settings` -> `Snap-ins` -> `Install Snap-in`.
 8. Define the `Connection`.
 9. Create an `Import.`
+
+
+## Creating keyrings
+
+Keyrings are a DevRev-specific mechanism for managing authentication for External Systems.
+They are called Connections in the DevRev app.
+
+They provide a secure way to store and manage credentials within your DevRev Snap-In.
+This eliminates the need to expose sensitive information like passwords
+or access tokens directly within your code or configuration files, enhancing overall security.
+
+Read more about Keyrings in the [developer documentation](https://developer.devrev.ai/snapin-development/references/keyrings).
+
+
+## Observability
+
+Workers are snap-ins, and they inherit observability methodology from snap-ins.
+
+To observe logs from your Worker in your development environment use `devrev snap_in_package logs | jq`.
+To open logs in your favorite editor use `devrev snap_in_package logs | code -`
+
+See also: https://developer.devrev.ai/snapin-development/debugging

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

@@ -1,6 +1,6 @@
 # Terminology
 
-## External System
+## External system
 
 An External System refers to any system (data source, CRM, etc.) that is not DevRev, e.g., Jira, Zendesk, HubSpot, etc.
 The External System ID is the identifier of an organization in the External System.
@@ -14,7 +14,7 @@ It allows our customers to bring in their existing data from [External Systems](
 sync data back to External Systems, and keep data in sync between DevRev and the External Systems.
 You can read more about Airdrop in the [general documentation](https://docs.devrev.ai/import#airdrop-features).
 
-## Snap-In
+## Snap-in
 
 A Snap-In is a component that extends DevRev’s functionality.
 It provides a base platform for creating [ADaaS Workers](#worker) ([Extractors](#extractor) and [Loaders](#loader)).
@@ -40,22 +40,22 @@ It is very similar to an [Extractor](#extractor), but it does the reverse job.
 
 An [Extractor](#extractor) or [Loader](#loader).
 
-## Forward Sync
+## Forward sync
 
 A Forward Sync is a sync from an [External System](#external-system) to DevRev.
 An [Extractor](#extractor) is used to extract the created and/or updated data from the [External System](#external-system).
 
-## Reverse Sync
+## Reverse sync
 
 A Reverse Sync is a sync from DevRev to an [External System](#external-system).
 A [Loader](#loader) is used to load the created and/or updated data to the [External System](#external-system).
 
-## Initial Import
+## Initial import
 
 An Initial Import is the first import of data from the [External System](#external-system) to DevRev.
 It is triggered manually by the end user in DevRev's Imports UI.
 
-## 1-way Sync
+## 1-way sync
 
 A 1-way Sync refers to an extraction, done after an [Initial Import](#initial-import) has been run.
 An [Extractor](#extractor) extracts data that was created and/or updated in the [External System](#external-system)
@@ -65,12 +65,12 @@ including any changes that occurred during the [Forward Sync](#forward-sync), bu
 An [Extractor](#extractor) must consult its state
 to get information on when the last successful [Forward Sync](#forward-sync) started.
 
-## Sync Unit
+## Sync unit
 
 A Sync Unit is the import/sync of a project, repository, etc., that is happening between DevRev and an [External System](#external-system).
 The Sync Unit ID is the unique identifier of the import/sync in DevRev.
 
-## External Sync Unit
+## External sync unit
 
 An External Sync Unit refers to a single unit in the [External System](#external-system) that we are airdropping to DevRev.
 In some systems, this is a project, in some it is a repository, in support systems this External Sync Unit could be called a brand or an organization.
@@ -83,7 +83,7 @@ while their enterprise plans may offer their clients to operate many separate un
 The External Sync Unit ID is the identifier of the project, repository, etc. in the [External System](#external-system).
 For GitHub, this would be the repository, i.e. `cli` in `github.com/devrev/cli`.
 
-## Sync Run
+## Sync run
 
 A Sync Run is one instance of an [Initial Import](#initial-import) any type of sync.
 If you do an import from Jira to DevRev, that import will be one Sync Run.
@@ -110,7 +110,7 @@ It constructs the Recipe based on the following inputs:
 - results of the schema discovery performed on raw data,
 - end-user inputs provided in the Mapping Screen during a [Sync Run](#sync-run).
 
-## Initial Domain Mapping
+## Initial domain mapping
 
 An Initial Domain Mapping is a JSON document that provides a list of possible mappings between the
 [External System](#external-system)'s domain model and the DevRev domain model.

fern/docs/pages/adaas/observability.mdx

@@ -128,9 +128,6 @@ navigation:
           - page: "Extraction Phases"
             slug: extraction-phases
             path: ../docs/pages/adaas/extraction-phases.mdx
-          - page: "Creating a Keyring"
-            slug: keyring
-            path: ../docs/pages/references/adaas/creating-a-keyring.mdx
           - page: "Extracting External Sync Units"
             slug: extract-external-sync-units
             path: ../docs/pages/adaas/extracting-external-sync-units.mdx
@@ -143,9 +140,6 @@ navigation:
           - page: "Extracting Attachments"
             slug: extract-attachments
             path: ../docs/pages/adaas/extracting-attachments.mdx
-          - page: "Obsevability"
-            slug: extract-attachments
-            path: ../docs/pages/adaas/observability.mdx
       - section: References
         slug: references
         contents: