Some word smithing and filled out two small sections.

Some word smithing and filled out two small sections about capabilities.

_episodes/02-identityRegistries.md

@@ -32,7 +32,7 @@ A key benefit to storing this information in a registry rather than a file, spre
 
 Despite the usefulness of registries, there is no universal incumbent product that is used. For many years, each university wrote its own identity registry to satisfy its own local use cases; many universities still take this approach. More recently, some universities have been working together to create a "Registry for Higher Education and Research" (with mixed success.) There also are newer enterprise and open source efforts have been aimed at organizations of different sizes. 
 
-We'll talk about capabilities later... key tools:
+We'll talk about capabilities later...some tools in this space include:
 
 * COmanage
 * midPoint
@@ -52,21 +52,17 @@ We'll talk about capabilities later... key tools:
 
 ## Some review: What is COmanage again?
 
-COmanage is a Membership Management Service. These tools provide many things:
+COmanage is a Collaboration Management Platform (CMP) designed and built for federated identity environments. These CMP tools provide many things:
 
 * An interface for user enrollment
 * The ability to assign rights and permissions to people through roles, groups, etc
 * The ability to distribute the management of rights and permissions to multiple people. _For example, a project's Principal Investigator can manage the rights and permissions for his/her project group_
 
-COmanage is not the only Membership Management Service. Examples of other services including HEXXA and PERUN.
+COmanage is not the only CMP focused on federated identity. Examples of other services include HEXXA and PERUN.
 
-Some will have strong preferences of one tool over another, though at their core, each of these tools serve the same basic functions. Their differences are primarily in the emphasis each tool makes on various features, how the development of the tool is managed, and how the tool is packaged with other tools.
+Deployers often strongly prefer one tool over another, though at their core, each of these tools serve the same basic functions. Their differences are primarily in the emphasis each tool makes on various features, how the development of the tool is managed, and how the tool is packaged with other tools.
 
-Since you are here, we are assuming that you have already made the choice to use COmanage.
-
---
-
-COmanage is a collaboration management platform designed for virtual organizations. With customizable enrollment flows, clear audit trails, and clear APIs that allow for integration with a variety of collaborative applications such as wikis, mailing lists, and more, COmanage provides VOs with an organized yet simple interface for identity and access management.
+Since you are here, we are assuming that you have already made the choice to invest in learning COmanage.
 
 ---
 

_episodes/03-whyCOmanage.md

@@ -30,16 +30,16 @@ COmanage is a key tool for several things:
 * Enrolling individuals into your Identity and Access Management systems in diverse ways
 * Combining information about a person that come from different sources into a single, comprehensive record
 * Modeling your organization as broad "groups" and attaching this group information to the combined identity records
-* Provisioning this information to other systems, either to use directly to manage access to systems or services, or to manage access via another tool like Midpoint or Grouper.
+* Provisioning this information to other systems, either to use directly to manage access to systems or services, or to manage access via another tool like midPoint or Grouper.
 
 ## Who uses COmanage?
 
 COmanage is usually used by one of two audiences:
 
-* Virtual Organizations (VOs) and groups that have straight-forward person enrollment and privileged setting needs. 
+* Virtual Organizations (VOs) and groups that have straight-forward person enrollment and privilege management needs. 
 This group usually can use COmanage directly to manage all aspects of enrolling individuals into their group using customized enrollment processes. In addition, because of the sophisticated ability to model organizations in COmanage, these VOs can usually can use this feature to provision access to systems and services without the need of another system.
 
-* Organizations with multiple source systems, individuals that assume multiple relationships to the organization (for example, a student and an employee), and/or organizations with more complicated organizational structures.
+* Organizations with multiple identity source systems, and where any particular person may have multiple affiliations with the organization (for example, a student and an employee), and/or organizations with more complicated organizational structures.
 This group usually has a more complicated time establishing a single record of information about an individual, either because the individual potentially has a more complicated relationship to the organization, or because individual relationships to the organization are complicated by temporal, location-based, or group management considerations.
 
 ## The architecture
@@ -78,4 +78,4 @@ PREVIOUS SECTION: [2. About Identity Registries](/_episodes/02-identityRegistrie
 
 LESSON OVERVIEW: [CO101 - Workshop Intro & Getting to Know COmanage](../index.md)
 
-WORKSHOP OVERVIEW: [COmanage Workshop: Managing Identities & Collaborations](https://github.internet2.edu/lpaglione/COmg-trainingOverview/blob/master/README.md)
+WORKSHOP OVERVIEW: [COmanage Workshop: Managing Identities & Collaborations](https://github.internet2.edu/lpaglione/COmg-trainingOverview/blob/master/README.md)

_episodes/04-capabilities.md

@@ -49,11 +49,11 @@ Once you have a single record for each of your users, you can use this informati
 
 ## Web SSO Capabilities
 
-... to be described ...
+Your identity registry should seamlessly integrate with whichever web SSO solution your organization leverages and not impose its own SSO requirements. COmanage is web SSO agnostic and can integrate with any SSO solution that integrates with Apache HTTP Server, including SAML (Shibboleth), OIDC (mod\_auth\_openidc), or even CAS.
 
 ## Efficiency Capabilities
 
-... API, Bulk operations, Search
+Today's identity management tools need to work the way you expect modern web tools to work and not get in your way. COmanage includes a RESTful API, supports bulk operations, and includes a fast and comprehensive search capability.
 
 ---
 
@@ -65,4 +65,4 @@ PREVIOUS SECTION: [3. What is COmanage](/_episodes/03-whyCOmanage.md)
 
 LESSON OVERVIEW: [CO101 - Workshop Intro & Getting to Know COmanage](../index.md)
 
-WORKSHOP OVERVIEW: [COmanage Workshop: Managing Identities & Collaborations](https://github.internet2.edu/lpaglione/COmg-trainingOverview/blob/master/README.md)
+WORKSHOP OVERVIEW: [COmanage Workshop: Managing Identities & Collaborations](https://github.internet2.edu/lpaglione/COmg-trainingOverview/blob/master/README.md)

_episodes/05-structure.md

@@ -18,7 +18,7 @@ nextEpisodeName:
 nextEpisodeURL: 
 ---
 
-# 5. How is COmanaged structured?
+# 5. How is COmanage structured?
 
 # People