Update headings as per guidelines

Author: shivansh

fern/docs/pages/custom-objects.mdx

@@ -1,30 +1,30 @@
-# Custom Objects
+# Custom objects
 
-## Table of Contents
+## Table of contents
 
 1. [Introduction](#custom-objects)
-2. [Quick Start](#quick-start)
-   - [Create a Schema and a Custom Object](#create-a-schema-and-a-custom-object)
-   - [Get a Custom Object](#get-a-custom-object)
-   - [List Custom Objects](#list-custom-objects)
-   - [Update a Custom Object](#update-a-custom-object)
-   - [Delete a Custom Object](#delete-a-custom-object)
-3. [Key Concepts](#key-concepts)
-4. [Custom Object Lifecycle](#custom-object-lifecycle)
+2. [Quick start](#quick-start)
+   - [Create a Schema and a custom object](#create-a-schema-and-a-custom-object)
+   - [Get a custom object](#get-a-custom-object)
+   - [List custom objects](#list-custom-objects)
+   - [Update a custom object](#update-a-custom-object)
+   - [Delete a custom object](#delete-a-custom-object)
+3. [Key concepts](#key-concepts)
+4. [Custom object lifecycle](#custom-object-lifecycle)
 
 - - -
 
 ## Introduction
-Custom objects allow you to extend DevRev's data model beyond the standard use-cases served by the native apps (build, support, etc).
-Custom Objects allow you to create and manage object types tailored to your specific business needs.
+Custom objects allow you to extend DevRev's data model beyond the standard use-cases served by the native apps like Build and Support.
+Custom objects allow you to create and manage object types tailored to your specific business needs.
 
-## Quick Start
+## Quick start
 
 Let's say you want to manage marketing campaigns on DevRev. We'll go through the process of creating a "Campaign" custom object with relevant fields.
 
 All DevRev objects require a schema. So, we'll first create a schema for the "Campaign" custom object. Make sure to replace the `<YOUR_API_TOKEN>` with your actual API token.
 
-### Create a Schema and a Custom Object
+### Create a schema and a custom object
 
 ```
 curl --location 'https://api.devrev.ai/schemas.custom.set' \
@@ -120,9 +120,9 @@ The response of the above API call will be the ID of the custom object created.
 
 Note that the `id` field in the above response is the system generated ID for the custom object.
 
-The sections below provide more details on the available API endpoints for interacting with Custom Objects.
+The sections below provide more details on the available API endpoints for interacting with custom objects.
 
-### Get a Custom Object
+### Get a custom object
 
 To get a custom object, use the `custom-objects.get` endpoint:
 
@@ -136,7 +136,7 @@ curl --location 'https://api.devrev.ai/custom-objects.get' \
 }'
 ```
 
-### List Custom Objects
+### List custom objects
 
 To list custom objects, use the `custom-objects.list` endpoint:
 
@@ -155,7 +155,7 @@ curl --location 'https://api.devrev.ai/custom-objects.list' \
 }'
 ```
 
-### Update a Custom Object
+### Update a custom object
 
 To update an existing custom object, use the `custom-objects.update` endpoint.
 The following example updates the budget of the previously created campaign custom object:
@@ -173,7 +173,7 @@ curl --location 'https://api.devrev.ai/custom-objects.update' \
 }'
 ```
 
-### Delete a Custom Object
+### Delete a custom object
 
 To delete a custom object, use the `custom-objects.delete` endpoint.
 The following example deletes the previously created campaign custom object:
@@ -188,7 +188,7 @@ curl --location 'https://api.devrev.ai/custom-objects.delete' \
 }'
 ```
 
-## Key Concepts
+## Key concepts
 
 1. **Leaf Type**: The base type of your custom object (e.g., "campaign").
 2. **Subtype**: A more specific categorization within a leaf type (e.g., "promotion" or "advertising" for a "campaign" leaf type).
@@ -197,7 +197,7 @@ curl --location 'https://api.devrev.ai/custom-objects.delete' \
 
 For more details on customization concepts, please refer to the [Customization](./object-customization) documentation.
 
-## Custom Object Lifecycle
+## Custom object lifecycle
 
 1. **Creation**: Define the leaf type, subtype (optional), and custom fields for your custom object.
 2. **Usage**: Create, update, and query custom objects as needed in your workflows.