From 5cfb332a34140424eb154b104b5267a10f7d2536 Mon Sep 17 00:00:00 2001
From: "Henry H. Andrews" <andrews_henry@yahoo.com>
Date: Thu, 17 Jul 2025 16:48:11 -0700
Subject: [PATCH] Fix missing space

---
 src/oas.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/oas.md b/src/oas.md
index c3b6b33141..bb12953cc2 100644
--- a/src/oas.md
+++ b/src/oas.md
@@ -309,7 +309,7 @@ Using a `contentEncoding` of `base64url` ensures that URL encoding (as required
 
 The `contentMediaType` keyword is redundant if the media type is already set:
 
-* as the key for a [MediaType Object](#media-type-object)
+* as the key for a [Media Type Object](#media-type-object)
 * in the `contentType` field of an [Encoding Object](#encoding-object)
 
 If the [Schema Object](#schema-object) will be processed by a non-OAS-aware JSON Schema implementation, it may be useful to include `contentMediaType` even if it is redundant. However, if `contentMediaType` contradicts a relevant Media Type Object or Encoding Object, then `contentMediaType` SHALL be ignored.