fix formatting issue + more diversity in examples

netmod-wg · Oct 10, 2024 · 658ab05 · 658ab05
1 parent c5c59b7
commit 658ab05
Showing 1 changed file with 11 additions and 11 deletions.
diff --git a/draft-ietf-netmod-schedule-yang.md b/draft-ietf-netmod-schedule-yang.md
@@ -563,10 +563,10 @@ This section uses the template described in {{Section 3.7 of ?I-D.ietf-netmod-rf
 
 ## The "generic-schedule-params" Grouping
 
-   {{ex-0}} illustrates the example of a requested schedule that needs to start no earlier than
-   08:00 AM, January 1, 2025 and end no later than 8:00 PM, January 31, 2025 (Beijing time).
-   Schedule requests that fail to meet the requirements are ignored by the system as indicates by
-   "discard-action".
+{{ex-0}} illustrates the example of a requested schedule that needs to start no earlier than
+08:00 AM, January 1, 2025 and end no later than 8:00 PM, January 31, 2025 (Beijing time).
+Schedule requests that fail to meet the requirements are ignored by the system as indicates by
+"discard-action".
 
 ~~~~
 {
@@ -580,17 +580,17 @@ This section uses the template described in {{Section 3.7 of ?I-D.ietf-netmod-rf
 ~~~~
 {: #ex-0 title="Generic Parameters with "max-allowed-end" for Schedule Validation"}
 
-    To illustrate the difference between "max-allowed-end" and "validity" parameters,
-    {{ex-00}} shows the example of a requested schedule that needs to start no earlier than
-    08:00 AM, January 1, 2025 (Beijing time). Schedule requests that fail to meet the
-    requirements are discarded with warning messages. The requested schedule may end
-    after 8:00 PM, January 31, 2025, but any occurrences that are generated
-    after that time would be considered as invalid.
+To illustrate the difference between "max-allowed-end" and "validity" parameters,
+{{ex-00}} shows the example of a requested schedule that needs to start no earlier than
+08:00 AM, January 1, 2025 (Paris time). Schedule requests that fail to meet the
+requirements are discarded with warning messages. The requested schedule may end
+after 8:00 PM, January 31, 2025, but any occurrences that are generated
+after that time would be considered as invalid.
 
 ~~~~
 {
   "example-sch-usage-1:generic-schedule-params": {
-    "time-zone-identifier": "China/Beijing",
+    "time-zone-identifier": "France/Paris",
     "validity": "2025-01-31T20:00:00",
     "min-allowed-start": "2025-01-01T08:00:00",
     "discard-action": "ietf-schedule:warning"