Committing the changes from today

_episodes/01-COperson.md

@@ -18,10 +18,11 @@ The information stored in the :gear: `CO Person` object typically includes
 
 * The organization or collaboration of which the person is a part (in the form of an identifier)
 * The person's status within that organization or collaboration
-* Minimal information about the person including the person's preferred time zone and date of birth.
+* Minimal information about the person including the person's preferred time zone and date of birth, list of physical addresses.
 * List of names
 * List of identifiers
 * List of email addresses
+* list of physical addresses
 
 This object also is connected to several other structural items that we will talk about in this lesson, including
 
@@ -30,6 +31,8 @@ This object also is connected to several other structural items that we will tal
 * **Group Memberships** - membership in a specific COmanage organizational object called a :gear" `CO Group`. We will learn more about :gear" `CO Groups` in a later lesson.
 * **Authenticators** - methods for the person to sign into COmanage
 
+---
+
 # CO Person status
 
 Each :gear: `CO Person` object has a status attached to it. This status is a calculated value based on the person's status in each of the Roles that the person has assumed in your organization or collaboration. We will review the calculation method when we talk about Roles. Status can be changed manually, or can change automatically based on conditions that you may set, or by workflows that you put in place.
@@ -78,13 +81,19 @@ When storing email addresses, more than one can be associated with the :gear: `C
 * **delivery** -  the delivery location (e.g., mailbox). _LDAP attribute: mailForwardingAddress_
 * **forwarding** - Address to forward mail to, perhaps if there is no delivery address, or an official or personal address is not functioning. _LDAP attribute: mailForwardingAddress_
 
-# Hands on
+# About physical addresses
+
+This information is not used by COmanage, but since it is handy to have physical address information in your registry, it is included. Any number of physical addresses may be associated with a :gear" `CO Person` object.
+
+---
+
+# Hands on - Starting our person model
 
 ![Interactive system activity](../assets/img/hands-on-keyboard.png)
 
-As we build our understanding of how people are modeled in COmanage, we will use people in your organization as examples. In your printed packet, there are sheets for :memo: **Modeling People**.
+As we build our understanding of how people are modeled in COmanage, we will use people in your organization as examples. In your printed packet, there are sheets for [ :memo: Modeling People](/files/handouts/CO310_ExamplePerson.pdf).
 
-Think of at least three people in your organization that you can use as examples. The three that you choose should assume different roles in your organization or collaboration. Maybe they have different levels of authority, have access to different kinds of systems or services, form and manage their own groups.
+Think of at least three people in your organization that you can use as examples. The three that you choose should assume different roles in your organization or collaboration. Maybe they have different levels of authority, have access to different kinds of systems or services, form and manage their own groups. One of the people you choose may even work for a different organization, though collaborates with individuals in your organization.
 
 Once you have thought about who you will use as your examples, write their names (or an alias!) on the sheets, one name per sheet. The name goes in the center circle that is labeled "CO Person".
 
@@ -105,15 +114,15 @@ OBJECT | DESCRIPTION
 
 WORKSHEET | DESCRIPTION
 --------- | -----------
-[ :memo: Modeling People](link_to_a_PDF_in_files>handouts) | Planning sheet used in this lesson for understanding how to model people in COmanage. This sheet is used to organize how specific people and their relationships would be expressed within COmanage
+[ :memo: Modeling People](/files/handouts/CO310_ExamplePerson.pdf) | Planning sheet used in this lesson for understanding how to model people in COmanage. This sheet is used to organize how specific people and their relationships would be expressed within COmanage
 
 ## Slides
 
 To be included
 
 ---
 
-NEXT SECTION: [The OrgIdentity Object](/_episodes/02-orgIdentity.md)
+NEXT SECTION: [2. The OrgIdentity Object](/_episodes/02-orgIdentity.md)
 
 LESSON OVERVIEW: [CO310 - Modeling People in COmanage](../index.md)