diff --git a/docs/hsds/use_cases.md b/docs/hsds/use_cases.md
index 3c4e1b5..871730b 100644
--- a/docs/hsds/use_cases.md
+++ b/docs/hsds/use_cases.md
@@ -5,14 +5,14 @@ Use Cases
 This page is *non-normative*, which means that it doesn't form part of the standard; if there is any ambiguity, the standard takes precedence. This page may be updated at any time in response to community demand.
 ```
 
-Open Referral's agenda is set by the prerogatives of a set of four types of users: 
+Open Referral's agenda is shaped by the prerogatives of four types of users: 
 
 * help seekers;
 * service providers;
 * researchers/analysts;
 * database administrators. 
 
- Read more about each of these personas in [our Types of Use / User Personas documentation](https://docs.openreferral.org/en/latest/initiative/index.html?highlight=types%20of%20use#types-of-use-and-user-personas). 
+Read more about each of these types of users in [the User Personas documentation](../initiative/index,md#types-of-use-and-user-personas). 
 
 In practice, we find that the primary type of user for HSDS and its associated tools are *Database Administrators*. It is still important for us to understand the needs of other types of end users – however we often process this understanding through the lense of Data Administrators to support them directly meeting the needs of end users.
 
diff --git a/docs/hsds/using_profiles.md b/docs/hsds/using_profiles.md
index a4e0147..c903d88 100644
--- a/docs/hsds/using_profiles.md
+++ b/docs/hsds/using_profiles.md
@@ -12,13 +12,13 @@ To this end, HSDS provides the [Profiles mechanism](profiles) which allows the c
 
 Profiles may do the following:
 
-* extend the HSDS specification by:
+* extend HSDS by:
   * adding new optional or mandatory fields
   * adding new validation rules (including making optional fields 'required')
   * adding new structures
   * adding new API endpoints to the API specification
   * recommending the use of particular value sets such as taxonomies or enumerations.
-* overriding or removing parts of the HSDS specification†:
+* overriding or removing parts of HSDS†:
   * remove fields and their validation rules
   * remove entire schemas/Tables/Objects
   * remove API endpoints from the API specification