ServiceNow link edits

Author: jastr945

website/docs/cloud-docs/integrations/service-now/service-graph/customizations.mdx

@@ -1,5 +1,5 @@
 ---
-page_title: Overview - ServiceNow Service Graph Connector for Terraform Integration - summary of the setup process
+page_title: Overview - ServiceNow Service Graph Connector for Terraform Integration - instructions on customizations for admins
 description: >-
   ServiceNow Service Graph Connector for Terraform allows you to edit ETL mapping and add more resources.
 ---
@@ -18,7 +18,7 @@ Any customizations should be done from the application's scope: **Service Graph
 
 ## Clone the ETL map
 
-Navigate to the **IntegrationHub ETL** in the top menu. Check the **SG-Terraform** record and click **Duplicate**.
+Navigate to the **IntegrationHub ETL** in the top menu. Check the **SG-Terraform** record and click **Duplicate**. Refer to the [ServiceNow documentation](https://docs.servicenow.com/en-US/bundle/utah-servicenow-platform/page/product/configuration-management/task/duplicate-cmdb-transform-map.html) on creating a duplicate of an existing ETL transform map.
 
 ## Build a resource in Terraform Cloud
 
@@ -44,25 +44,25 @@ Locate the resource in the state object. This JSON record will serve as a source
 
 ## Identify the CI target
 
-Pick a suitable Configuration Item (CI) target for your resource. For example, AWS virtual private network (VPC) is mapped to Cloud Network (`cmdb_ci_network`) in the Service Graph Connector for Terraform. Refer to the [ServiceNow CMDB documentation](https://docs.servicenow.com/en-US/bundle/utah-servicenow-platform/page/product/configuration-management/reference/cmdb-tables-details.html) for more details on available CI tables.
+Pick a suitable Configuration Item (CI) target for your resource. For instance, the AWS virtual private network (VPC) resource is mapped to Cloud Network (`cmdb_ci_network`) by the Service Graph Connector for Terraform. Refer to the [ServiceNow CMDB documentation](https://docs.servicenow.com/en-US/bundle/utah-servicenow-platform/page/product/configuration-management/reference/cmdb-tables-details.html) for more details on available CI tables.
 
 ## Consult the CI Class Manager
 
 After selecting an appropriate CI target, it is important to consult the CI Class Manager for guidance on dependent relationships. Numerous CMDB resources rely on other CI tables. If a related class is not properly mapped, the ETL job will generate errors or warnings, resulting in the failure of importing your resource into CMDB.
 
 In the top navigation, click on **All**, search for **CI Class Manager**, and click on **Open Hierarchy**. Search for your target CI Class and check **Dependent Relationships** tab to learn more about dependent mappings required by the resource.
 
-Example: according to the CI Class Manager, Cloud Network should be hosted on Logical Datacenter and Cloud Service Account.
+Example: according to the **CI Class Manager**, **Cloud Network** should be hosted on **Logical Datacenter** and **Cloud Service Account**.
 
 ## Set the mapping rules
 
-Open the **IntegrationHub ETL** from the top navigation menu and select your cloned ETL record prepared for customization. 
+Open the **IntegrationHub ETL** from the top navigation menu and select your cloned ETL map record prepared for customization. Refer to the [ServiceNow documentation](https://docs.servicenow.com/en-US/bundle/utah-servicenow-platform/page/product/configuration-management/concept/create-etl-transform-map.html) for a more comprehensive instruction on creating an ETL transform map.
 
 Click on the first **Specify Basic Details** section of the ETL Transform Map Assistant. Select the import set number containing your resource from the **Sample Import Set** dropdown and click **Mark as Complete**.
 
 Open the **Preview and Prepare Data** section and review the imported rows. Click **Mark as Complete**.
 
-The third section provides the interface for mapping resource attributes. Click on **Select CMDB Classes to Map Source Data**. Click on **Add Conditional Class** button at the top. Set the rules that will identify your resource in the import set. Use the `type` field value from the Terraform state object to identify your resource (on the ServiceNow side field name are prefaced with `u_`). Set the target CMDB CI CLass name and click **Save**.
+The third section provides the interface for mapping resource attributes. Click on **Select CMDB Classes to Map Source Data**. Click on **Add Conditional Class** button at the top. Set the rules that will identify your resource in the import set. Use the `type` field value from the Terraform state object to identify your resource (on the ServiceNow side, field name are prefaced with `u_`). Set the target CMDB CI CLass name and click **Save**.
 
 ![ServiceNow Service Graph Connector: setting the Conditional Class rules in the ETL mapping](/img/docs/service-now-service-graph-conditional-class-mapping.png)
 
@@ -78,7 +78,7 @@ Click **Mark as Complete** to finalize the **Select CMDB Classes to Map Source D
 
 ## Set the required relationships
 
-Click **Add Relationships** to proceed to the next section. Click **Add Conditional Relationship** button at the top. The following configuration tells the ETL that when a record with `aws_vpc` type is found in the import set, it should be hosted on **AWS Datacenter 1**. Click **Save**.
+Click **Add Relationships** to proceed to the next section. Click **Add Conditional Relationship** button at the top of the page. The following configuration tells the ETL that when a record with `aws_vpc` type is found in the import set, it should be hosted on **AWS Datacenter 1**. Click **Save**.
 
 ![ServiceNow Service Graph Connector: setting dependent relationships in the ETL mapping interface](/img/docs/service-now-service-graph-etl-setting-relationship.png)
 
@@ -90,4 +90,4 @@ Click **Mark as Complete** to finalize the **Add Relationships** section.
 
 ## Run a test
 
-You can test the new resource mapping either by using the **Test and Rollback Integration Results** interface of the ETL Transform Map Assistant or initiating a new run in your Terraform Cloud workspace containing the resource deployment.
+To test the new resource mapping, you have two options. First, you can utilize the **Test and Rollback Integration Results** interface of the ETL Transform Map Assistant. Alternatively, you can initiate a new run in your Terraform Cloud workspace that includes the deployment of the resource.

website/docs/cloud-docs/integrations/service-now/service-graph/index.mdx

@@ -17,9 +17,9 @@ The integration is based on the [Service Graph Connector](https://www.servicenow
 
 The diagram below shows how the application connects Terraform Cloud to your ServiceNow instance. 
 
-![screenshot: ServiceNow Service Graph Connector for Terraform design diagram](/img/docs/service-now-service-graph-design.png)
+![ServiceNow Service Graph Connector for Terraform: design diagram](/img/docs/service-now-service-graph-design.png)
 
-The Service Graph Connector for Terraform integrates with Terraform Cloud in order to obtain the latest information about your deployments, with the Terraform state being the source of data. The application doesn't make any requests to your cloud provider, and therefore doesn't ask you to share any cloud credentials.
+The Service Graph Connector for Terraform integrates with Terraform Cloud to fetch up-to-date information about your deployments. It leverages the Terraform state as the primary data source. The application doesn't make any requests to your cloud provider or require you to share any cloud credentials.
 
 ### Two modes of import
 
@@ -35,13 +35,13 @@ Access the scheduler by searching for **Service Graph Connector for Terraform**
 
 As a more lightweight alternative to the scheduled import, you can configure [webhook notifications](https://developer.hashicorp.com/terraform/cloud-docs/workspaces/settings/notifications) for all relevant workspaces in your Terraform Cloud. Webhooks offer an event-based approach to importing your resources. The import is triggered as soon as a Terraform run is successfully completed in the Terraform Cloud.
 
-Webhook POST requests are sent to an API endpoint exposed by the Service Graph Connector for Terraform in your ServiceNow instance. Each webhook request includes an HMAC token, and the endpoint validates the signature using the secret you provide. Learn more about [Terraform Cloud notification authenticity](https://developer.hashicorp.com/terraform/cloud-docs/workspaces/settings/notifications).
+Webhook POST requests are sent to an API endpoint exposed by the Service Graph Connector for Terraform in your ServiceNow instance. Each webhook request includes an HMAC token, and the endpoint validates the signature using the secret you provide. Learn more about [Terraform Cloud notification authenticity](https://developer.hashicorp.com/terraform/cloud-docs/workspaces/settings/notifications#notification-authenticity).
 
 Internally, the application uses a scheduled job as a helper to keep track of the incoming webhook requests. You can activate, configure it, and view the history of all webhook imports by navigating to **Scheduled Imports** and selecting **SG-Terraform Scheduled Process State**. By default, the job is set to run every minute. You can change it to run more frequently if you wish to process the webhook requests even faster.
 
 -> **Tip:** Both import options may be enabled, or you may choose to configure only the webhooks or the scheduled import. 
 
-The [setup page](/terraform/cloud-docs/integrations/service-graph/service-graph-setup) provides configuration details for both import modes.
+The [setup page](/terraform/cloud-docs/integrations/service-now/service-graph/service-graph-setup) provides configuration details for both import modes.
 
 ### ETL (Extract, Transform, Load)
 
@@ -93,6 +93,4 @@ The [resource mapping](/terraform/cloud-docs/integrations/service-now/service-gr
 
 ### Destroyed resources
 
-The Service Graph Connector automatically marks the deleted resources as **Non-Operational** in the ServiceNow CMDB. After the destroy run is completed in Terraform Cloud and the application's import job is finished in your ServiceNow instance, the value of the **Operational Status** field will change to **Non-Operational** for all resources removed from the Terraform state as a result of the deletion.
-
-
+The Service Graph Connector automatically marks the deleted resources as **Non-Operational** in the ServiceNow CMDB. After the destroy run is completed in Terraform Cloud and the application's import job is finished in your ServiceNow instance, the **Operational Status** field of all resources removed from the Terraform state during the deletion process will be updated to **Non-Operational**.

website/docs/cloud-docs/integrations/service-now/service-graph/resource-coverage.mdx

@@ -1,14 +1,14 @@
 ---
 page_title: Overview - ServiceNow Service Graph Connector for Terraform Integration - Resource Coverage
 description: >-
-  ServiceNow Service Graph integration allows to import selected resources into ServiceNow CMDB.
+  ServiceNow Service Graph integration allows to import selected resources from major cloud providers into ServiceNow CMDB.
 ---
 
 # Resource Coverage and Mapping
 
-The following tables outline how Service Graph Connector for Terraform maps resources from the Terraform state to the ServiceNow CMDB configuration items (CIs).
+The tables provided on this page illustrate the mapping of resources from the Terraform state to the ServiceNow CMDB configuration items (CIs) by the Service Graph Connector for Terraform.
 
-While the default ETL map provided by the application can be utilized without modification, it is also possible to customize it according to the specific requirements of your organization. Check [ETL Mapping Customizations](/terraform/cloud-docs/integrations/service-now/service-graph/customizations) for more details.
+While the default ETL map provided by the application can be utilized without modification, it is also possible to customize it according to the specific requirements of your organization. Check [customizations](/terraform/cloud-docs/integrations/service-now/service-graph/customizations) for more details.
 
 ## AWS
 

website/docs/cloud-docs/integrations/service-now/service-graph/service-graph-setup.mdx

@@ -18,7 +18,7 @@ The ServiceNow Service Graph for Terraform is a certified scoped application ava
 
 -> **ServiceNow roles:** `admin`, `x_hashi_service_gr.terraform_user`
 
-Once the integration is installed, proceed to the guided setup form to enter your Terraform credentials and set up a secure connection between Terraform Cloud and your ServiceNow instance.
+Once the integration is installed, you can proceed to the guided setup form where you will enter your Terraform credentials. This step will establish a secure connection between Terraform Cloud and your ServiceNow instance.
 
 ### Create and scope Terraform API token
 
@@ -39,17 +39,17 @@ In the **Configure Terraform authentication credentials** section, click **Confi
 
 If you want to route traffic between your Terraform Cloud and the ServiceNow instance through a MID server acting as a proxy, change **Applies to** dropdown to "Specific MID servers" and select your previously configured MID server name from the list. If you don't use MID servers, leave the default value.
 
-Set the **API Key** to the Terraform Cloud team API token that you created earlier in this tutorial and click **Update**.
+Set the **API Key** to the Terraform Cloud team API token that you created in the previous section and click **Update**.
 
 ![ServiceNow Service Graph Connector API Key Credentials configuration screen. The API key is provided, then saved by clicking the Update button](/img/docs/service-now-service-graph-apikey.png)
 
 In the **Configure Terraform authentication credentials** section, click **Mark as Complete**.
 
 ### Configure Terraform Webhook Notification token
 
-This section is optional and can be skipped if you plan to use only the scheduled import. Refer to the documentation explaining the [two modes of import](/terraform/cloud-docs/integrations/service-graph/index#two-modes-of-import) to decide which option works best for your environment.
+This section is optional and can be skipped if you plan to use only the scheduled import. Refer to the documentation explaining the [two modes of import](/terraform/cloud-docs/integrations/service-now/service-graph#two-modes-of-import) to decide which option works best for your environment.
 
-To improve security, Terraform Cloud includes an HMAC signature on all "generic" webhook notifications using a user-provided **token**. This token is an arbitrary secret string that Terraform Cloud uses to sign each webhook notification. ServiceNow uses the same token to verify the request authenticity. Refer to [Notification Authenticity](/terraform/cloud-docs/api-docs/notification-configurations#notification-authenticity) for more information.
+To improve security, Terraform Cloud includes an HMAC signature on all "generic" webhook notifications using a user-provided **token**. This token is an arbitrary secret string that Terraform Cloud uses to sign each webhook notification. ServiceNow uses the same token to verify the request authenticity. Refer to [Terraform Cloud notification authenticity](/terraform/cloud-docs/api-docs/notification-configurations#notification-authenticity) for more information.
 
 Create a token and save it in a safe place. This secret token can be any value but should be treated as sensitive.
 
@@ -123,10 +123,10 @@ Under the form, you will find a table containing all registered import sets. Loc
 
 Click on the **Import Set** field to open it and view its details. The **Outbound Http Requests** tab lists all requests made by your ServiceNow instance to Terraform Cloud in order to retrieve the latest Terraform state.
 
-Monitor the state of the import job. Wait for it to change to Complete, indicated by a green mark.
+Monitor the state of the import job. Wait for it to change to **Complete**, indicated by a green mark.
 Once the import job is complete, you can access the imported resources in the CMDB.
 
-![ServiceNow Service Graph Connector successful import set with completed state](/img/docs/service-now-service-graph-import-set.png)
+![ServiceNow Service Graph Connector: import set with successfully completed status](/img/docs/service-now-service-graph-import-set.png)
 
 You can also access all import sets, regardless of the import type, by navigating to **All** and selecting **Import Sets** under the **Advanced** category.