diff --git a/website/docs/app-directory/spec.md b/website/docs/app-directory/spec.md
index 107244603..37c6279ac 100644
--- a/website/docs/app-directory/spec.md
+++ b/website/docs/app-directory/spec.md
@@ -32,12 +32,12 @@ An FDC3 Standard compliant App Directory implementation **MUST**:
   - `/v2/apps` (GET)
   - `/v2/apps/{appId}` (GET)
 - Ensure that `appId` field values assigned to applications are unique within the directory.
-- Ensure that app directory records served meet the minimum requirements specified in the [app directory OpenAPI specification](pathname:///schemas/next/app-directory.html#tag/Application)
+- Ensure that app directory records served meet the minimum requirements specified in the [app directory OpenAPI specification](pathname:///schemas/next/app-directory.html#tag/Application).
 - Support retrieval of app directory records via either the raw `appId` (e.g. `myAppId`) or fully-qualified appId (e.g. `myAppId@host.domain.com`) as defined in the [app directory overview](overview#shrinking-the-uri).
 
 An FDC3 Standard compliant App Directory implementation **SHOULD**:
 
-- Support authentication (where required) via the HTTP Authorization header and Bearer authentication schema (implemented via JWT tokens)
+- Support authentication (where required) via the HTTP Authorization header and Bearer authentication scheme (implemented via JWT tokens)
 - Select any `categories` field values from the recommended list.
 - Encourage the use of the `lang` and `localizedVersions` fields in appD records to support localization and accessibility.