From 27d8dfa3f880450f4bbfebd5f0c9a4d1a30669f3 Mon Sep 17 00:00:00 2001
From: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Date: Fri, 17 Nov 2023 19:32:32 -0500
Subject: [PATCH] Massaging text for default language and direction

Rereading made me aware that some important words were omitted. I believe this to be editorial and clarification. Hopefully other readers will concur.
---
 index.html | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/index.html b/index.html
index f156ad19b..ed85f7ed0 100644
--- a/index.html
+++ b/index.html
@@ -5766,13 +5766,13 @@ <h3>Language and Base Direction</h3>
         <h3>Providing Default Language and Direction</h3>
 
         <p>
-The language and base direction of each natural language string property SHOULD
-be provided, either via the language value structure for each property or via a
-default language and base direction for the entire credential. Using the
-language value structure is preferred, because document defaults can result in
-a requirement that downstream processors perform JSON-LD expansion-based
-transformation which is otherwise optional. See the <a
-data-cite="JSON-LD#string-internationalization">String Internationalization</a>
+The language and base direction of each natural language string property value
+SHOULD be provided, either via the language value structure for each property 
+value, or via a default language and base direction for all values in the entire
+credential. Using the per-value language value structure is preferred, because
+using document defaults can result in a requirement that downstream processors
+perform JSON-LD expansion-based transformation which is otherwise optional. See the
+<a data-cite="JSON-LD#string-internationalization">String Internationalization</a>
 section of the [[JSON-LD]] specification for more information. Natural language
 string values that do not have a language associated with them SHOULD be
 treated as if the language value is `undefined` (language tag "`und`"). Natural