Added review feedback.

Author: Tom Moore

ToolGuides/toolkit-for-refactoring/02-Getting-Started/02-assessing-application.md

@@ -1,7 +1,6 @@
 # Assessing your application
 
-The first step in using the AWS Toolkit for .NET Refactoring to refactor your application from .NET Framework 4.8 to .NET 6 is to perform
-an assessment of the current application. This assessment will scan through your application code, dependencies and NuGet packages to help determine the level of complexity with converting your application. 
+The first step in using the AWS Toolkit for .NET Refactoring to refactor your application from .NET Framework 4.8 to .NET 6 is to perform an assessment of the current application. This assessment will scan through your application code, dependencies, and NuGet packages to help determine the level of complexity with converting your application. 
 
 The assessment is nondestructive, the results of the assessment is a report.
 
@@ -43,11 +42,11 @@ After configuring the toolkit, you are presented with the Refactoring Dashboard.
 
 ![Dashboard - Not Started](img/dashboard-not-started.png)
 
-At this point, the Assessment is listed as "Not Started." As a result other toolkit functionality may not be available. In order to perform an assessment, you fist need to open one of the code files in the solution. Double click on the "HomeController.cs" file to open it, then click back on the Dashboard Window.
+At this point, the Assessment is listed as "Not Started." As a result other toolkit functionality may not be available. In order to perform an assessment, you first need to open one of the code files in the solution. Double click on the "HomeController.cs" file to open it, then click back on the Dashboard Window.
 
 ![Dashboard - Not Started](img/open-code-file.png)
 
-From this window select the option to "Start Assessment" abd the toolkit will begin inspecting your application.
+From this window select the option to "Start Assessment" and the toolkit will begin inspecting your application.
 
 ![Dashboard - Not Started](img/assessment-in-progress.png)
 
@@ -59,13 +58,13 @@ Once your assessment is complete, you will receive an assessment report below.
 
 ### Incompatible NuGet packages
 
-This lists the number of packages that as included in the solution that are not compatible with the target version of .NET in this case .NET 6. Note that for these packages, you will need to find alternatives for the required functionality. 
+This lists the number of packages that are included in the solution that are not compatible with the target version of .NET in this case .NET 6. Note that for these packages, you will need to find alternatives for the required functionality. 
 
 ### Incompatible APIs
 
 This lists the number of API calls that are not portable to the new version of .NET. This may be cases where functionality has been deprecated or the API calls have breaking changes. Manual coding effort will be required, after porting, to make the code compatible with the new target version of .NET.
 
-These options provide hints to the amount of manual work, that the toolkit was able to identify, requred after the porting. It is important to understand that these are the incompatibilities that the tool was able to identify, it is not necessarily all of the changes that will be required. You may find code that needs to be reworked when you test your application after porting.
+These results provide details to the amount of manual work, that the toolkit was able to identify, that will be required after the porting. It is important to understand that these are the incompatibilities that the tool was able to identify, it is not necessarily all of the changes that will be required. You may find code that needs to be reworked when you test your application after porting.
 
 Further details of the incomparable code can be found by looking at the error list, and selecting to view Warnings. Each item in the list shows some manual effort that you will have to complete.
 

ToolGuides/toolkit-for-refactoring/03-porting-application/01-porting-application.md

@@ -6,7 +6,7 @@ Porting application code is destructive. You can't undo the changes once the pro
 
 ## Start porting your application
 
-You start the porting process for your application from the assessment dashboard. Select the project to be ported in the Solution Explorer, then click the Port drop down, and click "Port selected project."
+You start the porting process for your application from the assessment dashboard. Select the project to be ported in the Solution Explorer, then click the Port drop down, and click "Port Selected Project."
 
 ![Start Assessment](img/start-porting.png)
 

ToolGuides/toolkit-for-refactoring/03-porting-application/02-manual-refactoring.md

@@ -1,6 +1,6 @@
 # Manual Post-Porting refactoring
 
-Once your application has been refactored by the toolkit, you will have to go through a process of manually refactoring any of the incomparable code that the toolkit was not able to automatically correct for you.
+Once your application has been refactored by the toolkit, you will have to go through a process of manually refactoring any of the incompatible code that the toolkit was not able to automatically correct for you.
 
 This section of the guide will walk through some of the manual effort required for completing the porting of this application.
 
@@ -12,11 +12,11 @@ aws-net-guides\SampleApplications\2022\MediaCatalog\MediaLibrary6.0
 
 ## Fixing the missing NuGet packages
 
-When you open up code files that reference the AWS SDKs you will notice errors with the using clauses in the code. This will cause code errors with classes that cannot be found.
+When you open up code files that reference the AWS SDKs you will notice errors with the using clauses in the code, and other errors indicating that classes that your code uses can not be found.
 
 ![Error List](img/s3-storage-class-errors.png)
 
-These errors are caused by missing NuGet. These errors are corrected by adding the list of required AWS SDKs back into the project via NuGet. Right click on your project, select "Manage NuGet Packages..." and then add the following packages to your project.
+These errors are caused by missing NuGet packages. These errors are corrected by adding the list of required AWS SDKs back into the project via NuGet. Right click on your project, select "Manage NuGet Packages..." and then add the following packages to your project.
 
 * AWSSDK.Core
 * AWSSDK.S3