asked changes

Author: psharma-1909

src/connections/destinations/catalog/actions-singlestore/index.md

@@ -27,19 +27,19 @@ This destination is maintained by SingleStore. For any issues with the destinati
 {% include components/actions-fields.html %}
 
 ### Finding your SingleStore connection settings
-To connect Segment to SingleStore, use the SingleStore Data API (typically on port 443). Follow these steps to enable and locate your Data API connection settings:
+To connect Segment to SingleStore, use the SingleStore Data API (typically on port `443`). Follow these steps to enable and locate your Data API connection settings:
 
 1. Head to the [SingleStore Portal](https://portal.singlestore.com){:target="_blank"}.
 2. Select **Deployments**.
-3. Choose your Workspace and Database within the list of Deployments
-4. From the Connect dropdown, select **Connect to your own app**. SingleStore will display the the key settings you need to connect your SingleStore database to Segment. 
+3. Choose your **Workspace** and **Database** within the list of deployments
+4. From the **Connect** dropdown, select **Connect to your own app**. SingleStore will display the the key settings you need to connect your SingleStore database to Segment. 
 
-**Note:**  
+**Note**:  
 - The Data API is enabled by default for all SingleStore Cloud workspaces.  
-- Segment always uses the Data API (typically on port 443).  
-- If you are using a self-hosted or development SingleStore deployment (such as the SingleStore-dev image), the Data API may run on a different port. Refer to your deployment’s documentation or settings to confirm the correct port.
+- Segment always uses the Data API (typically on port `443`).  
+- If you use a self-hosted or development SingleStore deployment (such as the SingleStore-dev image), the Data API may run on a different port. Refer to your deployment’s documentation or settings to confirm the correct port.
 
-For more details, see the [SingleStore Data API documentation](https://docs.singlestore.com/cloud/reference/data-api/){:target="_blank"}.
+For more information, see the [SingleStore Data API documentation](https://docs.singlestore.com/cloud/reference/data-api/){:target="_blank"}.
 
 ## Database structure
 Segment writes data to your specified table in SingleStore (by default, this is `segment_data`) using the following schema:
@@ -48,10 +48,10 @@ Segment writes data to your specified table in SingleStore (by default, this is
 | -------- | ------ |  ----------- |
 | `messageId` |	TEXT |	A unique identifier for the event to ensure there is no duplication. |
 | `timestamp` |	Datetime(6) |	The timestamp of when the event was generated |
-| `type` |	TEXT |	The type of the event (e.g., "track", "identify", "page", "screen", "group", "alias"). |
-| `event` |	TEXT |	The name of the event. Only required for "track" events. |
+| `type` |	TEXT |	The type of the event (for example, Track, Identify, Page, Screen, Group, or Alias). |
+| `event` |	TEXT |	The name of the event. Only required for Track events. |
 | `name` |	TEXT |	The name of the page or screen. |
-| `properties` | JSON |	The properties of the track, page or screen event. |
+| `properties` | JSON |	The properties of the Track, Page or Screen event. |
 | `userId` |	TEXT |	The user ID associated with the event. |
 | `anonymousId` |  TEXT |	The anonymous ID associated with the event. |
 | `groupId` |  TEXT |	The group ID associated with the event. |
@@ -71,17 +71,17 @@ This query allows you to extract specific nested properties from the JSON column
 
 ## Troubleshooting
 
-> **Note:**  
+> info " 
 > The SingleStore Data API has a limit of 1MB per request. If a batch of events sent by Segment exceeds this limit, you may see an error similar to:
 > 
 > ```
 > Error reading request body: http: request body too large
 > ```
 > 
-> If you encounter this error, reduce the batch size in your Segment destination settings.
+> If you encounter this error, reduce the batch size in your Segment destination settings."
 
 
-### Connection Errors
+### Connection errors
 If you're unable to connect to the SingleStore database:
 * Verify that the credentials are correct.
 * Ensure that your SingleStore database is accessible from Segment’s servers.
@@ -92,20 +92,20 @@ If you encounter authentication errors when Segment attempts to connect:
 * Confirm that the Username and Password are correct.
 * Ensure that the user has the necessary permissions to write to the database.
 
-### Data Not Appearing in SingleStore
+### Data not appearing in SingleStore
 If events are not recorded in the specified table:
 * Verify that your sources are correctly sending data to Segment.
 * Check the event types to ensure they are supported.
 * Review your SingleStore database logs for any errors.
 
-## Frequently Asked Questions
+## Frequently asked questions
 ### Can I customize the schema used in SingleStore?
 
 By default, the mapping stores all fields from the Segment event in separate columns in the `segment_data` table. If you prefer, you can customize the mapping to selectively include or exclude specific fields to be sent and written into SingleStore.
 
 ### How does SingleStore handle data types from Segment?
 
-All event data is stored natively as JSON in the message column. This allows for flexible schema management and easy access to nested properties using SQL queries.  SingleStore's ability to dynamically and quickly parse the JSON allows all types of complex events to be queried or used in notebooks.
+Event data is stored as JSON in the message column. This allows for flexible schema management and easy access to nested properties using SQL queries.  SingleStore's ability to dynamically and quickly parse the JSON allows all types of complex events to be queried or used in notebooks.
 
 ### Is the data ingestion process real-time?