Merge pull request #920 from ritza-co/edit-1075-customize-fresh

1075: Proofread customize-freshservice.mdx

Author: bethh0rn

docs/integration/external-integrations/freshservice-integration/customize-freshservice.mdx

@@ -112,15 +112,15 @@ Typically, the first `<field>` represents the Device42 data returned from the qu
 - `resource`: The same as the `target` value.
 - `source-type`: Not functionally critical; this provides the data type displayed on the [integration app's **Data Mapping Chart**](#data-mapping-between-device42-and-freshservice).
 - `target`: The Device42 field to be mapped to Freshservice. The Freshservice convention is to use the display name in snake case, occasionally with the ID of the asset type as a suffix. For example, `memory_max_usage` and `memory_reservation_used`. The sync process determines the ID. Please look up which target field names to use in the [Freshservice API documentation](https://api.freshservice.com/). 
-- `escape`: This is used on field elements where `target="name"`. Some characters used in Device42 names aren't supported in Freshservice and need to be substituted. When creating a new task, you can set this to `true` but disable it if mismatching issues occur.
+- `escape`: This is used on field elements where `target="name"`. Some characters used in Device42 names aren't supported in Freshservice and need to be substituted. When creating a new task, you can set this to `true`, but disable it if mismatching issues occur.
 
 :::tip
 Use our InsightsAI chat under **Analytics > InsightsAI** to interpret DOQL query snippets quickly in the context of the Device42 data tables.
 :::
 
 ### Additional Matching Criteria for Updating Existing Items
 
-Some `<task>` elements in `mapping.xml` have a helper `<matching>` element for updating synched data that currently exists in Freshservice but may have slightly different name formats. For example, asset-type syncing tasks include the `<matching>` element to determine which query fields are used to match which asset attributes when trying to find a match. For example:
+Some `<task>` elements in `mapping.xml` have a helper `<matching>` element for updating synced data that currently exists in Freshservice but may have slightly different name formats. For example, asset-type syncing tasks include the `<matching>` element to determine which query fields are used to match which asset attributes when trying to find a match. For example:
 
 <details>
   <summary>Click to expand the code block</summary>
@@ -190,7 +190,7 @@ For a quick look at all the valid Freshservice `types`, see the [The `<task>` El
 | Copy AWS EBS from Device42 to Freshservice | asset | 19.04.00 |  |
 | Copy AWS Key Pair from Device42 to Freshservice | asset | 19.04.00 |  |
 | Copy AWS S3 from Device42 to Freshservice | asset | 19.04.00 |  |
-| Copy AWS Public IP from Device42 to FreshService | asset | 19.04.10 |  |
+| Copy AWS Public IP from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy Azure VPC from Device42 to Freshservice | asset | 19.04.00 |  |
 | Copy GCP Subnet from Device42 to Freshservice | asset | 19.04.00 |  |
 | Copy GCP VPC from Device42 to Freshservice | asset | 19.04.00 |  |
@@ -213,23 +213,23 @@ For a quick look at all the valid Freshservice `types`, see the [The `<task>` El
 | Copy GCP Network Interface from Device42 to Freshservice | asset | 19.04.00 |  |
 | Copy Azure Resource Group from Device42 to Freshservice | asset | 19.04.00 |  |
 | Copy AWS Image from Device42 to Freshservice | asset | 19.04.00 |  |
-| Copy Azure Public IP from Device42 to FreshService | asset | 19.04.10 | 19.04.99 |
-| Copy Azure Public IP from Device42 to FreshService | asset | 19.05.00 |  |
+| Copy Azure Public IP from Device42 to Freshservice | asset | 19.04.10 | 19.04.99 |
+| Copy Azure Public IP from Device42 to Freshservice | asset | 19.05.00 |  |
 | Copy GCP Image from Device42 to Freshservice | asset | 19.04.00 |  |
-| Copy GCP BigQuery Table from Device42 to FreshService | asset | 19.04.10 |  |
+| Copy GCP BigQuery Table from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy Azure Key Vault from Device42 to Freshservice | asset | 19.04.00 |  |
 | Copy VMware VCenter Resource Pool from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy VMware VCenter Network from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy VMware VCenter Disk from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy VMware VCenter Datastore from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy VMware VCenter Datacenter from Device42 to Freshservice | asset | 19.04.10 |  |
-| Copy AWS K8 Pod from Device42 to FreshService | asset | 19.04.10 |  |
+| Copy AWS K8 Pod from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy AWS K8s Namespace from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy AWS K8s Deployment from Device42 to Deployment | asset | 19.04.10 |  |
 | Copy AWS K8s Service from Device42 to Service | asset | 19.04.10 |  |
 | Copy AWS K8s Daemon Set from Device42 to Daemon Set | asset | 19.04.10 |  |
-| Copy AWS K8s Replica Set from Device42 to FreshService | asset | 19.04.10 |  |
-| Copy AWS K8s Cron Job from Device42 to FreshService | asset | 19.04.10 |  |
+| Copy AWS K8s Replica Set from Device42 to Freshservice | asset | 19.04.10 |  |
+| Copy AWS K8s Cron Job from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy GCP Public IP from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy AWS K8s Config Map from Device42 to Config Map | asset | 19.04.10 |  |
 | Copy AWS K8s Stateful Set from Device42 to Stateful Set | asset | 19.04.10 |  |
@@ -509,7 +509,7 @@ Set the `enable` attribute to `false` on those `<task>` elements:
     <task enable="false" name="Device Contract Associations" type="contract_asset" description="Create association between asset and contract">
     ```
 
-3. If you want to disable Software Licensing from being synced, find the `Copy Software Licensing info from Device42 to Freshservice` task (around line `2437`):
+3. If you want to prevent software licensing from being synced, find the `Copy Software Licensing info from Device42 to Freshservice` task (around line `2437`):
 
     ![Line 2437](/assets/images/freshservice-integration/example-vscode-6.png)
 
@@ -563,7 +563,7 @@ Set the `enable` attribute to `false` on those `<task>` elements:
     <task enable="false" name="Software In Use" type="software_installation" description="Create Software Install from Software In Use" d42_max_version="16.18.02">
     ```
 
-3. Software Licensing from Device42 syncs to `contract` in Freshservice. Find and disable the `Copy Software Licensing info from Device42 to Freshservice` task (around line `2437`):
+3. Software licensing from Device42 syncs to `contract` in Freshservice. Find and disable the `Copy Software Licensing info from Device42 to Freshservice` task (around line `2437`):
 
     ![Line 2437](/assets/images/freshservice-integration/example-vscode-6.png)
 
@@ -644,4 +644,4 @@ If you want Device42 to update `asset_state` values, set `skip-update` to `"fals
         </value-mapping>
     </field>
     ```
-    </details>
+    </details>