diff --git a/docs/tutorials/API_Related/CAOS_SOAP_API/CAOS_with_CDI.md b/docs/tutorials/API_Related/CAOS_SOAP_API/CAOS_with_CDI.md
index 0404914ef400cc21de86f6101f44925eb978b7ae..23e5432beb96cdb8d5d2dd0c94a241446e1e1d67 100644
--- a/docs/tutorials/API_Related/CAOS_SOAP_API/CAOS_with_CDI.md
+++ b/docs/tutorials/API_Related/CAOS_SOAP_API/CAOS_with_CDI.md
@@ -1,6 +1,6 @@
 # Consuming CAOS data with Cloud Data Integration
 
-[CAOS](https://kb.wisc.edu/registrar/page.php?id=11753) (Curricular and Academic Web Services) is a SOAP API, organized primarily by curricular data. We can retrieve a person's curricular data if we have specific person identifiers, or we can retrieve curricular data like Programs, Classes, and Subjects. It is easiest to approach consuming CAOS data with a clear idea of what elements you are seeking and the identifiers required for requesting it.
+[CAOS](https://kb.wisc.edu/registrar/page.php?id=11753) (Curricular and Academic Web Services) is a SOAP API, organized primarily by curricular data. We can retrieve a student's curricular data if we have specific student identifiers, or we can retrieve curricular data like Programs, Classes, and Subjects. It is easiest to approach consuming CAOS data with a clear idea of what elements you are seeking and the identifiers required for requesting it.
 
 It is important to keep in mind while making your SOAP API mapping that IICS cannot use a SOAP API as a starting Source. It's a mid-stream Web Services source only. This is understandable because we need to provide the SOAP API information in order to retrieve data (for example, giving a person's PVI or NetID to retrieve their graduation date).