Corrections on URLs

benno · Nov 6, 2019 · 83c09ef · 83c09ef
1 parent a6b6c17
commit 83c09ef
Show file tree

Hide file tree

Showing 5 changed files with 7 additions and 7 deletions.
diff --git a/_episodes/01-COperson.md b/_episodes/01-COperson.md
@@ -89,7 +89,7 @@ This information is not used by COmanage, but since it is handy to have physical
 
 # Hands on - Starting our person model
 
-![Interactive system activity](../assets/img/hands-on-keyboard.png)
+![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 [ Modeling People :memo:](/files/handouts/CO310-ModelingPeople.pdf).
 

diff --git a/_episodes/02-orgIdentity.md b/_episodes/02-orgIdentity.md
@@ -91,7 +91,7 @@ API-based sources (API) | Used to associate registered people with information f
 
 # The Identity Source AND Identity Source Record Objects
 
-## :gear: Identity Source Object
+## `Identity Source`:gear: Object
 
 Source attributes (information), once gathered, is stored in `Identity Source`:gear: Objects. These objects contain details about how the source information should be processed and data gathered from the representation of the person at the source.
 
@@ -103,7 +103,7 @@ The information stored in `Identity Source`:gear: objects typically includes:
 
 In addition, specific data and attributes, customized for the source type, is attached to the `Identity Source`:gear: Object. 
 
-## :gear: Identity Source Records Object
+## `Identity Source Records`:gear: Object
 
 Information from an `Identity Source`:gear: is connected to a `Org Identity`:gear: object via an :gear" `Org Identity Source Record` object. These objects are also used to cache data from sources so that they are readily available. 
 
@@ -113,7 +113,7 @@ In addition to the links to the related `Org Identity`:gear: and :gear" `Org Ide
 
 # Hands on - Starting our person model
 
-![Interactive system activity](../assets/img/hands-on-keyboard.png)
+![Interactive system activity](/assets/img/hands-on-keyboard.png)
 
 Think about the sources outside of COmanage where you store information about the people you may be registering. Use the individuals that you wrote down on the [ Modeling People :memo:](/files/handouts/CO310-ModelingPeople.pdf) worksheet to think of specific examples.
 

diff --git a/_episodes/03-memberships.md b/_episodes/03-memberships.md
@@ -18,7 +18,7 @@ Understanding the the types of grouping that people in your organization or coll
 
 # Hands on - Considering how people are linked to your organization
 
-![Interactive system activity](../assets/img/hands-on-keyboard.png)
+![Interactive system activity](/assets/img/hands-on-keyboard.png)
 
 Consider the people that you have been working with on your worksheet [ :memo: Modeling People](/files/handouts/CO310-ModelingPeople.pdf). How are these individuals connected to your organization? Things to consider:
 

diff --git a/_episodes/04-permissions.md b/_episodes/04-permissions.md
@@ -65,7 +65,7 @@ _By default, these attributes are read only._
 
 # Hands on - Starting our person model
 
-![Interactive system activity](../assets/img/hands-on-keyboard.png)
+![Interactive system activity](/assets/img/hands-on-keyboard.png)
 
 Consider the people that you have been using as examples in your [ :memo: Modeling People](/files/handouts/CO310-ModelingPeople.pdf) worksheet. What permissions would each of these individuals have? 
 

diff --git a/_episodes/notUsed-attributes.md b/_episodes/notUsed-attributes.md
@@ -142,7 +142,7 @@ OR the following (required plus optional useful attributes):
 
 # Hands on - Starting our person model
 
-![Interactive system activity](../assets/img/hands-on-keyboard.png)
+![Interactive system activity](/assets/img/hands-on-keyboard.png)
 
 < TO BE UPDATED >