diff --git a/_episodes/02-generalFactors.md b/_episodes/02-generalFactors.md
index acae73a..190e353 100644
--- a/_episodes/02-generalFactors.md
+++ b/_episodes/02-generalFactors.md
@@ -28,18 +28,26 @@ COs can support one our more Collaborative Organization Units (COUs).
 
 ### COUs
 
-"Collaborative Organizations Units" allow you to define an organizational structure within a CO. The reason that you would divide your CO into COUs are because there are differences across your CO that necessitates different policies in one or more of the following:
+"Collaborative Organizations Units" allow you to define an organizational structure within a CO. While many organizations have natural groups within them, the reason that you would divide your CO into COUs are because there are differences across your CO that necessitates different policies in one or more of the following:
 
 * How individuals join and/or leave the group
 * There are different rules about how applications get provisioned or deprevisioned
+* Who manages person membership and privileges in the group
 * The information stored or used about members of the group 
 
-These COUs may be recognized collaborators like departments, divisions, projects; or they may be related to the privileges that those in the group may have, for example, alumni or parents.
-
 If your collaboration–a single entity with common goals–has unique requirements among the different groups and/or departments regarding how participants will join those parts of your collaborations, then, you have a CO that contains COUs. If you have only one common set of policies that define how individuals are added or removed from the CO, then you do not have COU even though you may have groups for simple access control.
 
+When you have COUs, they may represent recognized groups of collaborators like departments, divisions, projects; or they may be related to the privileges that those in the group may have, for example, alumni or parents. 
+
+> A COU relationship to a CO is similar to the way that LDAP OUs have a relationship within an O.
+
+#### An example - LIGO
+
+LIGO is a virtual organization with a concrete goal (discovering gravitational waves) and specific large equipment (the detectors) to help reach that goal. LIGO, however, is not a uniform, flat organization. Within LIGO, there are several smaller organizations. These smaller organizations have specific needs regarding how new people join in their groups, and yet, these smaller organizations all have something in common - the parent organization of LIGO, where access to the equipment and the data is controlled, where agreements may be signed with new organizations wanting to be a part of (or a partner of) LIGO. 
+
+Here, LIGO is represented as a CO, and the smaller organizations are represented by COUs.
 
-other ph of your real organization. provide additional flexibility and control for 
+### CO Departments
 
 ## What are the most common factors for modeling the groups of individuals in your organization