diff --git a/input/pagecontent/2-8-Extensions.md b/input/pagecontent/2-8-Extensions.md
index 84d71917..2d74f8e2 100644
--- a/input/pagecontent/2-8-Extensions.md
+++ b/input/pagecontent/2-8-Extensions.md
@@ -1,20 +1,20 @@
-The specification is not prescriptive about support for extensions. However, to support extensions, the specification reserves the name `extension` and will never define an element with that name, allowing implementations to use it to provide custom behavior and information. The value of an extension element SHALL be a pre-coordinated JSON object. For example, an extension on a notification could look like this:
-
-```json
-{
- "context": [{
-   "key": "patient",
-   "resource": {
-    "resourceType": "Patient",
-    "id": "ewUbXT9RWEbSj5wPEdgRaBw3"
-   }
-  },
-  {
-   "key": "extension",
-   "data": {
-    "user-timezone": "+1:00"
-   }
-  }
- ]
-}
-```
+The specification is not prescriptive about support for extensions. However, to support extensions, the specification reserves the name `extension` and will never define an element with that name, allowing implementations to use it to provide custom behavior and information. The value of an extension element SHALL be a valid JSON object and is typically pre-coordinated. For example, an extension on a notification could look like this:
+
+```json
+{
+ "context": [{
+   "key": "patient",
+   "resource": {
+    "resourceType": "Patient",
+    "id": "ewUbXT9RWEbSj5wPEdgRaBw3"
+   }
+  },
+  {
+   "key": "extension",
+   "data": {
+    "user-timezone": "+1:00"
+   }
+  }
+ ]
+}
+```