Skip to content

Commit b209f6b

Browse files
authored
Merge pull request #895 from ritza-co/edit-169-cloud-endure
169: Proofread cloud-endure-device42.mdx
2 parents b978541 + 3b99a76 commit b209f6b

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/reports/reports/cloud-endure-device42.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ sidebar_position: 5
66
import ThemedImage from '@theme/ThemedImage'
77
import useBaseUrl from '@docusaurus/useBaseUrl'
88

9-
After you have performed your HyperVisors / \*nix/ Windows scans and associated your business applications to your devices using the Device42 Business Application functionality, you are ready to prepare for your migration to AWS using CloudEndure.
9+
After you have performed your HyperVisors / \*nix / Windows scans and associated your business applications with your devices using the Device42 Business Application functionality, you are ready to prepare for your migration to AWS using CloudEndure.
1010

1111
Device42 has streamlined the process of conducting cloud migrations to AWS by integrating with the CloudEndure Blueprint. With a few short clicks, Device42 users can assess which workloads have the CloudEndure agent loaded as well as export blueprints for CloudEndure migrations.
1212

1313
## Here's How It Works
1414

15-
When performing a migration with CloudEndure, the first step is to ensure the CloudEndure agent is installed on the workloads in scope.  This can be easily viewed from the built-in **CloudEndure Prep** report.
15+
When performing a migration with CloudEndure, the first step is to ensure the CloudEndure agent is installed on the workloads in scope, which you can easily view from the built-in **CloudEndure Prep** report.
1616

1717
- Select **Analytics > Advanced Reporting**.
1818

@@ -44,9 +44,9 @@ After ensuring the workloads in scope have the CloudEndure agent installed, down
4444

4545
Once you have generated the CloudEndure **CSV** file from **Advanced Reporting**, you must make sure to download the [Mass Blueprint Setter](https://docs.cloudendure.com/Content/Scripts/CloudEndure%20mass%20blueprints%20setter.zip) script.
4646

47-
This script requires **Python2.7** to run, and in order to have the blueprint set in CloudEndure, the devices in the **CSV** file must have the CloudEndure agent installed and connected to your chosen project.
47+
This script requires **Python2.7** to run, and in order to have the blueprint set in CloudEndure, the devices in the **CSV** file must have the CloudEndure agent installed and be connected to your chosen project.
4848

49-
Before running the script, in the CloudEndure CSV file you must add the project name in the first column (**projectName**) for each device. Include the relevant name of the matching project for each listed machine.
49+
Before running the script, you must open the CloudEndure CSV file and add the project name in the first column (**projectName**) for each device. Include the relevant name of the matching project for each listed machine.
5050

5151
![](/assets/images/WEB-607_Cloud-Endure-4.png)
5252

@@ -73,9 +73,9 @@ optional arguments:
7373
```
7474
</details>
7575

76-
When ready to run, supply all of the above parameters. If there are any issues when running the script a `.log` file will be created in the same directory.
76+
When ready to run, supply all of the above parameters. If there are any issues when running the script, a `.log` file will be created in the same directory.
7777

78-
Once completed, all machines in the CSV file that match machines in CloudEndure will have their respective blueprints updated.
78+
Once completed, all the machines in the CSV file that match machines in CloudEndure will have their respective blueprints updated.
7979

8080
### Reference Links
8181

0 commit comments

Comments
 (0)