1251: Integrations pages grammar cleanup (Week 15, 2026)

docs/integration/api-overview.mdx

@@ -3,22 +3,23 @@ title: "API Overview"
 sidebar_position: 2
 ---
 
-Application Programming Interface (APIs) define a contract of service for a set of allowed operations. Device42 features comprehensive RESTful APIs as the primary method of entering, editing, and retrieving data externally and programmatically.
+Device42 provides RESTful APIs that you can use to create, update, and retrieve data programmatically. These APIs are the primary way to integrate Device42 with external systems and automation workflows.
+
+This page provides links to the current Device42 API documentation and to previous Swagger (OpenAPI) YAML files.
 
 :::info
-Please visit our **[API documentation](https://api.device42.com/)** for detailed information on using Device42 APIs.
+For endpoint details, request formats, and examples, see the **[Device42 API documentation](https://api.device42.com/)**.
 :::
 
-## Device42 Swagger Files
+## Download Previous Swagger Files
 
-The current version of the API is hosted at [api.device42.com](https://api.device42.com/).
+The current API version is hosted at [api.device42.com](https://api.device42.com/).
 
-You can find the previous versions of our Swagger (OpenAPI) YAML files below:
+You can download previous Swagger (OpenAPI) YAML files below:
 
 - <a href="/assets/files/d42-swagger-v190510.yaml" download>v19.05.10</a>  
 - <a href="/assets/files/d42-swagger-v190430.yaml" download>v19.04.30</a>  
 - <a href="/assets/files/d42-swagger-v190310.yaml" download>v19.03.10</a>  
 - <a href="/assets/files/d42-swagger-v190200.yaml" download>v19.02.00</a>  
 - <a href="/assets/files/d42-swagger-v190100.yaml" download>v19.01.00</a>  
 - <a href="/assets/files/d42-swagger-v190000.yaml" download>v19.00.00</a>
-

docs/integration/external-integrations/aperture-vista-to-device42-migration.mdx

@@ -3,44 +3,40 @@ title: "Aperture VISTA to Device42 Migration"
 sidebar_position: 1
 ---
 
-The Aperture VISTA to Device42 migration works in the following manner: Data is exported from the Aperture VISTA application by first creating Device42 custom views in the Aperture SQL Server database. These views are then exported from Aperture VISTA and saved as `.csv` or Excel files which are then easily imported and mapped into Device42's data architecture. 
+The Aperture VISTA to Device42 migration exports data from Aperture VISTA by creating Device42 custom views in the Aperture SQL Server database. These views are exported from Aperture VISTA and saved as `.csv` or Excel files, which are then imported and mapped into Device42’s data architecture.
 
-Aperture views can be downloaded here: [https://www.device42.com/migrations/aperture/](https://www.device42.com/migrations/aperture/).
+Device42 then automatically creates building, data center, and rack configurations for all rack-mounted devices. With the import completed, Device42’s agentless discovery tool automatically identifies and maps remaining IP-based network devices and intelligent power equipment for ongoing monitoring and management.
 
-Device42 then automatically creates building, data center, and rack configurations for all rack-mounted devices. With the import completed, Device42’s agentless autodiscovery tool automatically identifies and maps remaining IP-based network devices and intelligent power equipment for ongoing monitoring and management.
+[Download the Aperture VISTA views](https://www.device42.com/migrations/aperture/).
 
 ## Import View
 
-![Import Views](/assets/images/media_1437070133863.png)
-
-A long list of SQL views is available to give you the ability to pick and choose the information you want to migrate to Device42 from Aperture VISTA.
+A long list of SQL views lets you select the information you want to migrate from Aperture VISTA to Device42.
 
-[Download the Aperture VISTA views](https://www.device42.com/migrations/aperture/).
+![Import Views](/assets/images/media_1437070133863.png)
 
 ## Run View
 
-![Run View](/assets/images/media_1437070334329.png)
+Run the views to export data from your Aperture VISTA instance.
 
-By running the views you can easily get data out of your instance of Aperture VISTA.
+![Run View](/assets/images/media_1437070334329.png)
 
 ## Save Data to CSV or Excel
 
+Right-click anywhere on the data and select **Save Results As...**.
+
 ![Save Data to CSV or Excel](/assets/images/media_1437070455551.png)
 
-Right click anywhere on the data and select **Save Results As...**.
+## Save Your File
 
-## Saving Your File
+Give the file a name and save the data locally.
 
 ![Saving Your File](/assets/images/media_1437070573781.png)
 
-Give the file a name and save the data locally.
+## Download the Bulk Import Tool
 
-## Downloading the Bulk Import Tool to Map Fields
+[Download the bulk import tool](https://www.device42.com/bulk-data-management/) and use it to map your Aperture VISTA fields to Device42. For detailed instructions, see the [bulk import tool documentation](https://www.device42.com/blog/2015/07/02/bulk-import-your-data-from-any-format-easily-with-new-device42-import-tool/).
 
 ![Downloading the Bulk Import Tool to Map Fields](/assets/images/media_1437484542712.png)
 
-[Download the bulk import tool](https://www.device42.com/bulk-data-management/).
-
-For instructions on how to use the Bulk Import Tool to map your fields, see the [bulk import tool documentation](https://www.device42.com/blog/2015/07/02/bulk-import-your-data-from-any-format-easily-with-new-device42-import-tool/).
-
-If you have any questions, contact support at [support@device42.com](mailto:support@device42.com).
+Contact support at [support@device42.com](mailto:support@device42.com) with any questions.

docs/integration/external-integrations/azure-migrate.mdx

@@ -3,138 +3,144 @@ title: "Azure Migrate"
 sidebar_position: 2
 ---
 
-You can get to Azure Migrate directly @ [https://portal.azure.com/#create/Microsoft.AzureMigrate](https://portal.azure.com/#create/Microsoft.AzureMigrate)
+The Azure Migrate integration lets you assess and migrate servers to Azure using Device42 as the assessment tool. This page covers how to set up Device42 from the Azure Migrate portal, register an Azure Active Directory user, and export your business applications to Azure.
 
-## Setting up Device42 from the Azure Migrate Portal
+You can access Azure Migrate directly at [portal.azure.com](https://portal.azure.com/#create/Microsoft.AzureMigrate).
 
-1\. Begin by signing up for an Azure account if you don’t already have one. You’ll have to provide a credit card to verify your identity, and agree to the conditions to continue: 
+## Set Up Device42 From the Azure Migrate Portal
 
-![Microsoft Azure Migrate](/assets/images/azure_migrate_start_free.png)
+1. Begin by signing up for an Azure account if you don't already have one. You will have to provide a credit card to verify your identity and agree to the conditions to continue.
 
-2\. Click the button to continue to the Azure portal, and once there, choose “Assess and Migrate servers” as pictured below: 
+    ![Microsoft Azure Migrate](/assets/images/azure_migrate_start_free.png)
 
-![Sign up for Azure](/assets/images/agree_step_2b.png) 
+2. Click the button to continue to the Azure portal, and once there, choose **Assess and Migrate Servers**.
 
-![Continue to Azure Portal](/assets/images/Continue_to_Azure_Portal-3.png) 
+    ![Sign up for Azure](/assets/images/agree_step_2b.png)
 
-![Assess and Migrate Servers](/assets/images/Assess_and_migrate_servers-4.png) 3. Next, you’ll want to begin adding migration tools; click “Add a tool.” 
+    ![Continue to Azure Portal](/assets/images/Continue_to_Azure_Portal-3.png)
 
-![Add a tool](/assets/images/add_tool-5.png)
+    ![Assess and Migrate Servers](/assets/images/Assess_and_migrate_servers-4.png)
 
-4\. Choose an existing Resource Group, or click the “Create new” link (highlighted) to create a new one. The “Resource Group” name represents the group of machines you’ll be migrating, and can be a name of your choosing, but should be descriptive. Then click“OK.” 
+3. Click **Add a Tool** to begin adding migration tools.
 
-![Name your Migration Project](/assets/images/add_a_tool-5.1.png) 
+    ![Add a tool](/assets/images/add_tool-5.png)
 
-![Create resource group](/assets/images/add_a_tool-create-resource-group-5.2.png)
+4. Choose an existing Resource Group, or click **Create New** to create a new one. The resource group name represents the group of machines you will be migrating and should be descriptive. Then click **OK**.
 
-5\. Give your migration project a name, and when finished, click“Next” to continue. 
+    ![Name your Migration Project](/assets/images/add_a_tool-5.1.png)
 
-![Name the project](/assets/images/name_migration_project_5.3.png)
+    ![Create resource group](/assets/images/add_a_tool-create-resource-group-5.2.png)
 
-6\. Select Device42 as your Azure Migration assessment tool by clicking on it so it is selected as shown below. Click “Next” to choose Device42. 
+5. Give your migration project a name and click **Next** to continue.
 
-![Select Device42 as assessment tool](/assets/images/add_tool_select_D42-6.png)
+    ![Name the project](/assets/images/name_migration_project_5.3.png)
 
-7\. You can add a migration tool at this point if know which you want to use, but the default is to skip adding a migration tool for now (you can choose a tool when you are ready to migrate). Make sure the “Skip adding a migration tool for now” checkbox is checked, and click “Next” to continue. 
+6. Select Device42 as your Azure Migration assessment tool by clicking on it, then click **Next**.
 
-![Skip adding a migration tool](/assets/images/add_tool_skip_migration-6.1.png)
+    ![Select Device42 as assessment tool](/assets/images/add_tool_select_D42-6.png)
 
-8\. Review your tool choice(s) and then click “Add tool(s)” to continue. 
+7. You can add a migration tool at this point if you know which one you want to use. Otherwise, leave **Skip adding a migration tool for now** checked and click **Next**.
 
-![Review tool choices](/assets/images/review_add_tool-6.2.png)
+    ![Skip adding a migration tool](/assets/images/add_tool_skip_migration-6.1.png)
 
-You’ll see confirmation the deployment has been initialized.
+8. Review your tool choices and click **Add Tool(s)** to continue.
 
-9\. Click “Learn more” to head to the Device42 information page. 
+    ![Review tool choices](/assets/images/review_add_tool-6.2.png)
 
-![Intializing tool deployment](/assets/images/initializing_deployment-7.png)
+    You will see confirmation that the deployment has been initialized.
 
-10\. From the Device42 information page, click the orange “Try it now, free” button to jump over to the Device42 download page. 
+    ![Initializing tool deployment](/assets/images/initializing_deployment-7.png)
 
-![Learn more to install D42](/assets/images/Install_d42_trial-8.png)
+9. Click **Learn More** to go to the Device42 information page.
 
-11\. Fill out the form and click “Start your Free Trial” to download Device42. Your download should be e-mailed to you immediately. 
+    ![Learn more to install D42](/assets/images/Install_d42_trial-8.png)
 
-![Device42 download page](/assets/images/Click_for_D42_Download_FINAL.png)
+10. From the Device42 information page, click the orange **Try It Now, Free** button to go to the Device42 download page.
 
-For help installing Device42, head over to the Device42 documentation: [https://docs.device42.com](https://docs.device42.com). 1. The [Getting Started with Installation section is a great place to begin! [installation](getstarted/deploy-device42/index.mdx).
+11. Fill out the form and click **Start Your Free Trial** to download Device42. Your download link will be emailed to you.
 
-2\. Once you’ve installed, you’ll want to begin discovering your environment. See the “Getting started with autodiscovery” section of the documentation here: [getstarted/getting-started-with-auto-discovery.mdx](/getstarted/getting-started-with-auto-discovery.mdx).
+    ![Device42 download page](/assets/images/Click_for_D42_Download_FINAL.png)
 
-3\. When you’ve finished with discovery and assessment, you can export your discovered data back to Microsoft Azure. Instructions on exporting can be found here: [applications/business-services/building-business-services-in-device42.md#section-15](apps/business-services/building-business-services-in-device42.mdx#section-15).
+Once Device42 is installed, start discovering your environment:
+
+- For installation help, see the [Getting Started with Installation](/getstarted/deploy-device42) section of the documentation.
+- To begin discovering your environment, see [Getting Started with Discovery](/getstarted/getting-started-with-auto-discovery).
+- To export discovered data back to Microsoft Azure, see [Building Business Services in Device42](/apps/business-services/building-business-services-in-device42).
 
 * * *
 
-## Exporting your Business Apps to Azure for Migration
+## Export Your Business Apps to Azure for Migration
+
+Complete the following steps to register an Azure Active Directory user, collect the required credentials, and export your business applications from Device42.
 
-### Register an Azure Active Directory user
+### Register an Azure Active Directory User
 
-1\. Login to Azure Portal, and create an "App Registration" in Azure Active Directory. You'll need this user to authenticate to Azure when uploading your export. Create a User:
+1. Log in to the Azure portal and create an **App Registration** in Azure Active Directory. You will need this user to authenticate to Azure when uploading your export.
 
-![Create a new Azure User](/assets/images/register_an_application.png)
+    ![Create a new Azure User](/assets/images/register_an_application.png)
 
-2\. Create Client Secret and Save the value for Device42.
+2. Create a client secret and save the value for Device42.
 
-![Create a Client Secret](/assets/images/certificates_and_secrets.png)
+    ![Create a Client Secret](/assets/images/certificates_and_secrets.png)
 
-3\. Create a new Migration Project _(if you haven't already; see the prior section on this page)_.
+3. Create a new migration project if you haven't already (see the [prior section](#set-up-device42-from-the-azure-migrate-portal) on this page).
 
-![Search for Azure Migrate](/assets/images/search_azure_migrate.png)
+    ![Search for Azure Migrate](/assets/images/search_azure_migrate.png)
 
-4\. Under Subscriptions > Subscription > Access Control (IAM), click "Add" under Add a role assignment.
+4. Under **Subscriptions > Subscription > Access Control (IAM)**, click **Add** under **Add a Role Assignment**.
 
-5\. Select a "Contributor" role and type the name of the app registration in the "Select" text box (in this case, the name of our app was _dev\_device42_).
+5. Select the **Contributor** role and type the name of the app registration in the **Select** text box.
 
-6\. Select the app registration and Save. This gives the correct permissions to export data from Device42 to Azure.
+6. Select the app registration and click **Save**. This grants the correct permissions to export data from Device42 to Azure.
 
-![](/assets/images/Azure-Migrate_Add-Role-Assignment_App-Name.png)
+    ![](/assets/images/Azure-Migrate_Add-Role-Assignment_App-Name.png)
 
-### Collect required information from Azure
+### Collect Required Information From Azure
 
-**Collect the following information from Azure:**
+Collect the following information from Azure before exporting:
 
-1\. **Tenant ID:** Azure Active Directory -> Properties
+1. **Tenant ID:** **Azure Active Directory > Properties**
 
-![Azure Tenant ID](/assets/images/Tenant_ID.png)
+    ![Azure Tenant ID](/assets/images/Tenant_ID.png)
 
-2\. **Subscription ID:** Subscriptions
+2. **Subscription ID:** **Subscriptions**
 
-![Azure Subscription ID](/assets/images/subscription_ID.png)
+    ![Azure Subscription ID](/assets/images/subscription_ID.png)
 
-3\. **Client ID:** Azure Active Directory -> App registrations
+3. **Client ID:** **Azure Active Directory > App Registrations**
 
-![Azure Client ID](/assets/images/Client_ID.png)
+    ![Azure Client ID](/assets/images/Client_ID.png)
 
-4\. **Client Secret:** Saved from app registration creation.
+4. **Client Secret:** Saved from app registration creation.
 
-5\. **Migrate Project Name:** The name you chose when creating the project.
+5. **Migrate Project Name:** The name you chose when creating the project.
 
-### Export your Business Application(s) from Device42
+### Export Your Business Applications From Device42
 
-1\. Login to Device42 and go to Business Apps. Select one or more Business App(s) to export by checking the check-boxes next to them, and Choose ‘Create Migration for Selected Objects’.
+1. Log in to Device42 and go to **Business Apps**. Select one or more business apps to export by checking the checkboxes next to them, then choose **Create Migration for Selected Objects**.
 
-![Select business apps to export](/assets/images/Business_app_selection.png)
+    ![Select business apps to export](/assets/images/Business_app_selection.png)
 
-2\. Select ‘Azure’ as your _Target_ from the drop-down.
+2. Select **Azure** as your target from the dropdown.
 
-![Export to Azure selection](/assets/images/Export_Business_Apps.png)
+    ![Export to Azure selection](/assets/images/Export_Business_Apps.png)
 
-3\. Enter Migrate Project information from Azure collected in the last step.
+3. Enter the migration project information collected in the previous step.
 
-![Enter collected Azure prjoect details](/assets/images/Enter_project_Details.png)
+    ![Enter collected Azure project details](/assets/images/Enter_project_Details.png)
 
-4\. Click Export. Go back to the Azure Migrate Hub, and click 'Refresh.' You should now see your exported data in Azure!
+4. Click **Export**. Go back to the Azure Migrate Hub and click **Refresh**. Your exported data should now be visible in Azure.
 
-![Refresh the Azure Migrate Hub window](/assets/images/Azure_Hub_REFRESH.png)
+    ![Refresh the Azure Migrate Hub window](/assets/images/Azure_Hub_REFRESH.png)
 
-## Reviewing your Device42 exports in Azure Migrate
+## Review Your Device42 Exports in Azure Migrate
 
-After exporting your Business Applications from Device42 _(__as explained in the prior section)_ to the Azure Migrate portal, log back into the Azure Migrate portal, or refresh if you are already logged in. You should see something similar to the following example _(but with your data, of course)_.
+After exporting your business applications to the Azure Migrate portal, log back in (or refresh if already logged in). You should see your data displayed similarly to the following examples.
 
 ![Device42 Assessment details in Azure Example](/assets/images/Assessment_details_1.png)
 
 ![Device42 Assessment details in Azure Example](/assets/images/Assessment_details_2.png)
 
 ![Device42 Assessment details in Azure Example](/assets/images/Assessment_details_3.png)
 
-**If you need help with steps or processes discussed on this page and haven't found the answer here, please don’t hesitate to reach out to [support@device42.com](mailto:support@device42.com)!**
+Contact [support@device42.com](mailto:support@device42.com) if you need help with any steps on this page.