Fix all typos found in the project

Co-authored-by: k1ch <19498202+k1ch@users.noreply.github.com>

Author: Copilot

README.md

@@ -58,7 +58,7 @@ This list of links is written for developers that would like to contribute to Th
   * [X] The Usher's tokens contain roles corresponding to scoped permissions
   * [X] Refresh tokens with sessions (currently limited to one session per persona)
 * Data Model
-  * [X] Permissions assigned to personas via role assigment
+  * [X] Permissions assigned to personas via role assignment
   * [X] Permissions assigned directly to personas
   * [X] Support for individual personas (each identified by same `sub` claim) to have multiple optional "user_contexts"
 * API

docs/GLOSSARY.md

@@ -6,8 +6,8 @@
 
 - **User**: An individual, belonging to an organization, and identified by a unique subscriber ID. This ID could be provided by an ID provider like Auth0 or Salesforce, or be a natural ID like email address. Users use User Agents (like browsers) to access client applications.
 - **User Context**: The account context for a specific User. A User can have different accounts but be identified using the same subscriber ID. This allows the User to be identified in the context of the account in which they are operating.
-- **Tenant**: An organization identified by a unique issuer ID. Client Applications can be set up independently to separate different organizations (single tenant). Also, multiple organisations can use the same Client Application and are differentiated by an identifier on access (mutli-tenant). The Tenant in The Usher identifies individual organizations either by name or by their issuer claim.
-- **Persona**: The manifestation of a user on tenant.This has a very specific meaning in the context of The Usher. It is possible for a User to have access to Client Applications on different Tenants using the same sub_claim (for example their email address). The Usher allows for this by creating unique Personas linked to a tenant.
+- **Tenant**: An organization identified by a unique issuer ID. Client Applications can be set up independently to separate different organizations (single tenant). Also, multiple organizations can use the same Client Application and are differentiated by an identifier on access (multi-tenant). The Tenant in The Usher identifies individual organizations either by name or by their issuer claim.
+- **Persona**: The manifestation of a user on tenant. This has a very specific meaning in the context of The Usher. It is possible for a User to have access to Client Applications on different Tenants using the same sub_claim (for example their email address). The Usher allows for this by creating unique Personas linked to a tenant.
 - **Client** (Client Application): An application for which personas can be assigned entitlements. The client application may change its behavior based on the scope granted to it by a Resource Authorization Server. For example, the client may use the granted roles to determine what kind of UI to presented to the persona, and the client may receive different or limited responses from backends/APIs based on the granted permissions. Various contexts of an application may only require and request particular limited scope.
 - **Entitlement**: A role or a permission that is assigned to a persona (to which a persona is `entitled`).
 - **Group**: A tag applied to users and managed on the customer identity server. These tags can be carried in the ID/access token under the claim `groups` An organization's groups can be mapped to Application Roles by this Resource Authorization Server.

server/test/endpoint_admin_roles_permissions.test.js

@@ -88,7 +88,7 @@ describe('Admin Roles Permissions', () => {
       assert.equal(response.status, 401)
     })
 
-    it('should return 404 and for a non existing role key', async () => {
+    it('should return 404 for a non existing role key', async () => {
       const response = await fetch(`${url}/roles/${nonExistingRoleKey}/permissions`, {
         method: 'GET',
         headers: requestHeaders,