Word-smithing pass

Author: jhannahLCD

Docs/Introduction/Commands/Overview.md

@@ -1,29 +1,28 @@
 # CodeFactory Commands
 When working with CodeFactory you always start with commands. 
 Commands are the trigger point where all CodeFactory functionality starts from. 
-As of this release of CodeFactory all commands are triggered from context menus on individual nodes within solution explorer. As per the name a command following a command exection pattern. 
-This is made up of two methods that are raised from internal events that occur within Visual Studio itself. These events are trigged when a selected solution explorers item content menu is opened. 
-The following explain the two methods their goal and the different type of commands that are supported in CodeFactory.
+Currently all commands are triggered from context menus on individual nodes within solution explorer. Each ommand is made up of two methods that are raised from internal events that occur within Visual Studio itself. These events are trigged when a selected solution explorers item content menu is opened. 
+The following describes the two methods, their goals and the different type of commands that are supported in CodeFactory.
 
 ## Command Result
 Whenever a command is executed a real time data model is generated based on the type of Visual Studio object that has been selected. The data model is regenerated each time the target command is executed. 
 
 ## Enable Command
 When a command is first loaded it sends the command result to the enable method on the command.
-This method is called to allow the author of the command to determine if the command should be enabled to be used. 
-This was added to allow the author to control execution of automation. 
-You may only want automation to be enabled based on a target condition.
+This method is called to allow the author of the command to determine if the command should be visible to the automation user for use. 
+This feature exists in order to allow automation authors to control execution of automation by hiding or showing commands on the context menu as they desire. 
+
 This is controlled by simply returning a true or false value to determine if the command should be accessible.
 If enabled is true the command will show up in the context menu. 
-The developer in Visual Studio will then trigger the command to execute by selecting the context menu item.
+The developer in Visual Studio can then trigger the command to execute by selecting the context menu item.
 
 ## Execute Command
-Once the developer selects a command to be executed Visual Studio will trigger the execute method of the command itself. 
+Once the developer selects a command to be executed Visual Studio will run the execute method of the command itself. 
 Like before a real time data model is passed to the execute method. 
-This is where the automation process starts and whatever functionality has been assigned will executed at this time.
+This is where the automation process starts and whatever functionality has been authored will executed at this time.
 
 ## Solution Explore Commands
-CodeFactory current supports the trigger of commands from the solution explorer window in Visual Studio.
+CodeFactory current supports the trigger of commands from the Solution Explorer window in Visual Studio.
 The following are the supported Solution Explorer nodes that will CodeFactory Automation.
 
  - Solution Command - Generates a Solutiuon data model

Docs/Introduction/Data Models/Overview.md

@@ -1,16 +1,15 @@
 # CodeFactory DataModels
-The primary strength of CodeFactory is its ability to generate real time data models directly from the Visual Studio environment. 
+The primary strength of CodeFactory is its ability to generate real time data models directly from your project/solution artifacts within  the Visual Studio environment. 
 This ability makes it possible to do design time automation when delivering software. In this section we will provide a brief overview of the data models that are generated dynamically by the CodeFactory platform. These data models are used throughout the automation process.
 
 ## Data Models
-All data models are plain old CLR objects or POCO's for short. Each data model is implemented as an immutable data class. This approach is used since an change to the underlying data model requires a complete regeneration of the data model from the visual studio environment to make sure you have the latest version of all data.
-
-Data model generation is either triggered during the trigger of a new automation process, or from various CodeFactory API calls that will request new copies of data models.
+All data models are plain old CLR objects or POCO's for short. Each data model is implemented as an immutable data class. This approach is used since a change to the underlying data model requires a complete regeneration of the data model from the visual studio environment to make sure you have the latest version of all data.  For example, making a change to a C# class object would force CodeFactory to regenerate a data model of that file/class object.
 
+Data model generation is either triggered during the execution of a new automation process, or from various CodeFactory API calls that will request new copies of data models.
 
 ## Solution Explorer Models (Project System)
 The following models are directly generated off the legacy and new project systems that are hosted by Visual Studio.
-The overview of each data model is designed to provide an overview of capabilties. It will not list every single data element or function. See help docs for the full description if each data model.
+The overview of each data model is designed to provide an overview of capabilties. The examples here are not complete and only show partial functionality for the purpose of explanation.  Please see our help docs for the full description if each data model.
 
 ### Solution
 Data model that represents the loaded solution. This provides the location of the solution as well as access to the projects in the solution.
@@ -37,8 +36,8 @@ The C# source document project system access as well as full access to the C# so
 CodeFactory has access to the C# language compiler and can dynamically generate data models the represent the C# based source code. 
 CodeFactory provides direct access all the way down to member and type level data. 
 In addition, will give you direct access to the raw source code at the target object level. 
-The following are the data models that are generated whenever either accessing from source code files, or from directly referenced assemblies. 
-The overview of each data model is designed to provide an overview of capabilties. It will not list every single data element or function. See help docs for the full description if each data model.
+The following data models are generated whenever you are accessing from source code files, or from directly referenced assemblies. 
+The overview of each data model is designed to provide an example of capabilties and does not list every single data element or function. Please see our help docs for the full description if each data model.
 
 ### Soure Code
 The source code data model provides access to all elements that were compiled from the source code document. This includes the following.

Docs/Introduction/Environment/Overview.md

@@ -1,21 +1,21 @@
-# CodeFactory Environment
-CodeFactory is a collection of automation tools that are designed to be used in a native IDE enviornment. 
-The integration into the IDE environment is based on the fact that CodeFactory is a design time based tool.
-In this section we will focus on how CodeFactory integrates into the IDE.
+# CodeFactory Ecosystem
+CodeFactory is a collection of automation tools that are designed to be used in a native IDE(Integrated-Development-Environment). 
+The decision to integrate into the IDE is based on the fact that CodeFactory is a design time tool - meaning that no extra code artifacts or runtimes are required to be added to your final solution codebase.
 
-Through out the life of this product more then one IDE will be supported in future releases. Which is why CodeFactory is always named after the platform it is hosted on.
+Throughout the life of CodeFctory more then one IDE will be supported in future releases. Which is why CodeFactory is always named after the platform it is hosted on.
 
+In this section we will focus on how CodeFactory integrates into the IDE.
 
 ## CodeFactory for Visual Studio
 CodeFactory for Visual Studio is an extension of the Visual Studio IDE. 
 CodeFactory was designed to run as an internal service inside Visual Studio just like Razor, C#, or any number of other services that are part of Visual Studio. 
-This means that once installed CodeFactory is always on and will automatically execute automation that is loaded when a solution is loaded.
+This means that once installed CodeFactory is always 'on' and will automatically load automation commands for use when a solution is loaded.
 
 ## CFX - Code Factory Extension
-CodeFactory automation is saved as complete package in a single file called a CodeFactory extension. 
+A CodeFactory automation project is saved as complete package in a single file called a CodeFactory extension (*.cfx). 
 This uses a similar approach as word with DOCX or Excel with XSLX files. 
-The CodeFactory extension or CFX is a file that gets put in the root of the solution folder. 
-Once the solution is opened in Visual Studio it will automatically load the automation and make it avaiable to the solution.
+All it takes is to copy a CodeFactory extension, or CFX, file into the root of the your solutions folder. 
+Once the solution is opened in Visual Studio it will automatically load the automation and make it avaiable for use.
 
 ## CodeFactory SDK
 All automation for CodeFactory was designed and delivered using the CodeFactory SDK. 

Docs/Introduction/Overview.md

@@ -1,16 +1,15 @@
 # Overview of CodeFactory
-This provides an overview of the different capabilities and parts of the CodeFactory environment. 
-Each target area will provide a clear overview of target set of capabilites as well as guidance.
+This describes the different capabilities and parts of the CodeFactory ecosystem. Each area will provide a clear overview of target set of capabilites as well as guidance.
 
-This overview is designed to be read either top down or jump to the topic that interests you.
+This guide is designed to be read either top down or jump to the topic that interests you.
 
 ## CodeFactory for VisualStudio
 Review of the CodeFactory environment and how it integrates with Visual Studio.
 
 [Link Here]
 
 ## CodeFactory Platform
-Review of the different parts of the CodeFactory platform itself. These are used to drive CodeFactory also used in authoring CodeFactory automation.
+Review of the different parts of the CodeFactory platform itself. This decsribes what is used to drive CodeFactory also used in authoring CodeFactory automation.
 
 [Link Here]
 

README.md

@@ -2,15 +2,14 @@
 
 # What is CodeFactory?
 
-CodeFactory is real time software delivery tool that natively runs inside of Visual Studio. The focus of CodeFactory is to increase the delivery velocity of applications being built new or uplift of projects to other technologies.
+CodeFactory is real time software delivery tool that natively runs inside of Visual Studio. The focus of CodeFactory is to increase the delivery velocity of building new applications or the uplift/refactor of projects to other technologies.
 
 ## Automation of Construction Delivery Patterns
-One of the core goals of CodeFactory is to use application source code within the application as a data model.
-This is a similar concept to ORM mapping based tools. 
+One of the core features of CodeFactory is to use your application source code as a data model.  This is a similar concept to ORM mapping based tools. 
 
-This allows for the implementation of development patterns to auto generate common application code developers have to build by hand. The following are common usage scenarios, but by no means the only scenarios in use.
+This allows for the implementation of development patterns which can then auto generate common application code that developers would otherwise have to build by hand. The following common usage scenarios showcase this concept.  These are by no means the only scenarios in available.
 
-- Bounds checking in methods
+- Adding/Creating Bounds checking in methods
 - Implementation of exception handling logic
 - Implementation of standard logging
 - Automation of dependency injection
@@ -20,7 +19,7 @@ This allows for the implementation of development patterns to auto generate comm
 - Auto generation and mapping of logic between service technolgoies and consumers
 
 ## Automation of Technology Transformation
-Due to the design of CodeFactories SDK the tooling is very helpful in transformation of existing functionality of application to be lifted into new technology implementation. The following are common usage scenarios for technology transformation, like about these are not the only scenarios for usage.
+Due to the way in which the CodeFactory SDK was designed - the tooling is very helpful in transforming existing functionality of an application to a new technology implementation. The following are common usage scenarios for technology transformation - but like the Construction Patterns above are not the only scenarios for usage.
 
 - Read ORM based data classes and transform into POCO's or to other ORM based implementations
 - Read data classes and generate interface definitions for all classes
@@ -30,13 +29,13 @@ Due to the design of CodeFactories SDK the tooling is very helpful in transforma
 - Migration Mapping of logic from one system to another (Example using UI dialogs to select where logic comes from and where it goes in a new system)
 
 ## Designed for Different Delivery Approaches
-The CodeFactory tool directly integrates into the Solution Explorer in Visual Studio. This provides flexibility to the delivery team on when to use automation and how that automation should be triggered. The following are a few examples, like the others above not the only approaches that can be taken.
+CodeFactory directly integrates into the Solution Explorer in Visual Studio. This provides flexibility to the delivery team on when to use automation and how that automation should be triggered. The following are a few examples, much like the others above these are not the only approaches that can be taken.
 
 ### Contract Driven Approach
 Interfaces are defined and automation triggers when interfaces need to be implemented. Allowing for a interface based design of the system and the core shell of the entire delivery driven by interface implementations.
 
 ### UI Driven Approach
-User Interface dialogs are triggered and questions are asked which generates the impementation of new or uplift of application logic. 
+User Interface dialogs are defined and triggered as a part of an automation command and questions are asked which generates the impementation of new or uplift of application logic. 
 
 ### Event Driven Approach
 Changes in markup files or .net application code files like c# will trigger the option to execute automation logic to complete the implementation of logic. 
@@ -48,20 +47,18 @@ Logic is run that will rebuild the definition of a target artifact. This is a co
 This is the most common which uses a number of the above approaches together to meet a development teams delivery needs. 
 
 ## Zero Touch Delivery Tool
-CodeFactory runs inside of visual studio itself. Which means it acts more like a behind the scene compiler.
-CodeFactory is a design time tool and has no application runtime capabilties. 
-This means there is no application libraries or technologies that have to be included inside the application you are delivering. 
-Any artificates that are generated by CodeFactory appear to be standard developer hand written code. 
+CodeFactory runs inside of visual studio itself and it acts more like a behind the scenes compiler.  CodeFactory is a design time tool and has no application runtime capabilties. This means there is no application libraries or technologies that have to be included inside the application you are delivering. Any artificates that are generated by CodeFactory appear to be standard developer hand written code. 
 
 ## Designed to Build Team Customized Delivery
 CodeFactory is a team delivery tool, which means there is no one size fits all delivery process. Its a SDK style platform that simplifies the design of automation to be taken advantage of by delivery teams. 
 CodeFactory releases a standard set of automation libraries fully implemented. 
 The goal of these libraries is to provide standard guidance scenarios. 
 Alot of teams will want to extend and change the guidance. Which is exactly what this tool is designed for.
 
-The following are the core tooling capabilities of CodeFactory
+The following are the core capabilities of CodeFactory
+
 ### Solution and Project Management
-Direct access to the solution and project system hosted in visual studio. This will include access and partial management of the following items.
+Direct access to the solution and project system hosted inside of visual studio. This will include access and partial management of the following items.
 
 - Solution
 - Solution Folders
@@ -78,6 +75,7 @@ Direct access to any document that is hosted in the solution this will include t
  - Add/remove/replace content at target locations within the document
  - Add new documents
  - Remove documents
+ 
 ### C# Source Code Model Generation
 CodeFactory builds real time data models of C# code files. The models provide access to the following information