Fix typos and grammar

src/customer-guides/salesforce.mdx

@@ -84,7 +84,7 @@ Pick one way to connect, then grant the permissions below.
 
 ### Required system permissions
 
-The following system permissions need to be enabled the profile or permission set you configure, the sections below provides instructions on how to enable them.
+The following system permissions need to be enabled on the profile or permission set you configure. The sections below provide instructions on how to enable them.
 
 - **API Enabled**
 - If the integration includes real-time Subscribe Actions, also enable the [Subscribe Action permissions](#subscribe-action-permissions)
@@ -291,7 +291,7 @@ If the integration creates or updates custom fields in your Salesforce instance,
 
 - **API Enabled** - allows the integration to make API calls
 - **Modify Metadata Through Metadata API Functions** — allows the integration to call the Metadata API in order to modify custom fields
-- **Customize Application** — allow the creation and update of custom fields
+- **Customize Application** — allows the creation and update of custom fields
 - **Manage Profiles and Permission Sets** - allows a new permission set to be created to give the current user permission to read from and write to the field
 - **Assign Permission Sets** - allows the integration to assign the new permission set to the current user
 

src/notifications/overview.mdx

@@ -62,7 +62,7 @@ There are two ways to set up notifications:
    - Go to [Destinations](https://dashboard.withampersand.com/projects/_/settings/destinations/)
    - Click **New Destination** and configure:
      - **Name**: A descriptive name (e.g., "production-alerts")
-     - **Type**: Choose webhook, [Slack](/destinations/slack), Kinesis or Amazon S3
+     - **Type**: Choose webhook, [Slack](/destinations/slack), Kinesis, or Amazon S3
      - **Configuration**: Provide the endpoint URL or stream details
    - Click **Create Destination**
 

src/provider-guides/accuLynx.mdx

@@ -117,7 +117,7 @@ export function renderCellValue(value) {
 
 \* The connector will read all jobs - assigned and unassigned.
 
-\*\* For these objects, the connector will first enumerate all the jobs, and then list their children records. (e.g. For `jobs/financials`, the connector will first list all jobs, and then read the financials for all jobs.)
+\*\* For these objects, the connector will first enumerate all the jobs, and then list their child records. (e.g. For `jobs/financials`, the connector will first list all jobs, and then read the financials for all jobs.)
 
 <Note>
 **Writes are limited by AccuLynx's API:**

src/provider-guides/asana.mdx

@@ -80,7 +80,7 @@ Follow the steps below to create an Asana app and add
 ![Alt text](/images/provider-guides/9d9c63f-Asana2.gif)
 
 
-The **Basic information** section displays **Client ID** and **Client Secret** keys for your App. You'll use these credentials to connect your app to [Ampersand](https://docs.withampersand.com/docs/asana#add-your-asana-app-info-to-ampersand) . 
+The **Basic information** section displays **Client ID** and **Client Secret** keys for your App. You'll use these credentials to connect your app to [Ampersand](https://docs.withampersand.com/docs/asana#add-your-asana-app-info-to-ampersand).
 
 ## Add Your Asana App info to Ampersand
 

src/provider-guides/connectWise.mdx

@@ -283,7 +283,7 @@ For writes, provide custom fields as if they were native fields; the connector c
 
 You only need to include the custom fields you want to set or change. To clear a field, set its value to `null`.
 
-To find a custom field's ID, check a read response, custom fields are returned with their IDs in the `customFields` array.
+To find a custom field's ID, check a read response; custom fields are returned with their IDs in the `customFields` array.
 
 
 ### Example integration

src/provider-guides/goTo.mdx

@@ -53,7 +53,7 @@ For an example manifest file of a GoTo integration, visit our [samples repo on G
 
 
 ## Before you get started
-goto
+
 To integrate GoTo with Ampersand, you need to [Create a GoTo Account](https://developer.goto.com/signup/) and obtain the following credentials from your GoTo App:
 
 - Client ID

src/provider-guides/highlevel.mdx

@@ -48,7 +48,7 @@ The HighLevel connector supports writing to and reading to the following objects
 - [users](https://highlevel.stoplight.io/docs/integrations/7f581f780cf2f-users-api) (read, write)
 - [workflows](https://highlevel.stoplight.io/docs/integrations/070d2f9be5549-get-workflow) (read)
 - [locations/search](https://highlevel.stoplight.io/docs/integrations/12f3fb56990d3-search) (read)
-- [custom-menus](https://highlevel.stoplight.io/docs/integrations/e377daf40adc8-custom-menus-api  ) (read, write)
+- [custom-menus](https://highlevel.stoplight.io/docs/integrations/e377daf40adc8-custom-menus-api) (read, write)
 - [marketplace/billing/charges](https://highlevel.stoplight.io/docs/integrations/c8ed91df11efc-get-all-wallet-charges) (read)
 - [calendars/events/appointments](https://highlevel.stoplight.io/docs/integrations/a192f863cad27-create-appointment) (write)
 - [calendars/events/block-slots](https://highlevel.stoplight.io/docs/integrations/5a52896a68879-create-block-slot) (write)

src/provider-guides/hubspot.mdx

@@ -407,4 +407,4 @@ Share the [HubSpot customer guide](/customer-guides/hubspot) with your customers
 When you are ready to list on the HubSpot marketplace, follow the instructions in the [HubSpot documentation](https://developers.hubspot.com/docs/apps/developer-platform/list-apps/listing-your-app/listing-your-app).
 
 - For the **App Information** section, you should use information about your company, not about Ampersand.
-- For **Install Button URL**, use the URL of your application that users go to to start the installation process (this is usually where you've embedded the Ampersand UI Component).
+- For **Install Button URL**, use the URL of your application that users go to in order to start the installation process (this is usually where you've embedded the Ampersand UI Component).

src/provider-guides/jobber.mdx

@@ -127,7 +127,7 @@ Jobber also emits a handful of account-level topics that don't map to a subscrib
 
 ### Example integration
 
-For an example manifest file of an Jobber integration, visit our [samples repo on Github](https://github.com/amp-labs/samples/blob/main/jobber/amp.yaml).
+For an example manifest file of a Jobber integration, visit our [samples repo on Github](https://github.com/amp-labs/samples/blob/main/jobber/amp.yaml).
 
 ## Before you get started
 
@@ -166,7 +166,7 @@ Once your Jobber Developer account is ready, you need to create a Jobber applica
 
 5. Click **Save** to create your app.
 
-Upon creation, the app will display the necessary credentials: **Client ID** and **Client Secret.** Note these down, as you will need it to connect your app to Ampersand.
+Upon creation, the app will display the necessary credentials: **Client ID** and **Client Secret.** Note these down, as you will need them to connect your app to Ampersand.
 
 
 ## Add your Jobber app info to Ampersand

src/subscribe-actions.mdx

@@ -130,7 +130,7 @@ integrations:
 
 ### Other events
 
-Beyond the standard events that Ampersand supports, you have the ability to subscribe to any other event that that underlying platform supports. The event names listed in `otherEvents` must match the provider's raw event names exactly.
+Beyond the standard events that Ampersand supports, you have the ability to subscribe to any other event that the underlying platform supports. The event names listed in `otherEvents` must match the provider's raw event names exactly.
 
 For Salesforce this includes [events like](https://developer.salesforce.com/docs/atlas.en-us.change_data_capture.meta/change_data_capture/cdc_event_fields_header.htm):
 - `UNDELETE`