fixup! Update links.md

Signed-off-by: benjamin-j-powell <[email protected]>

links.md

@@ -156,10 +156,10 @@ While links can be sent separately, links can also be embedded in the CDEvent
 context as an optional field. Embedded links look similar to separate links
 except `START` links are not needed since we can infer when a chain has started
 based on the context of the event. This leaves only three types of links that
-may be embedded, `PATH`, `RELATION` and `END`. While `END` could be also inferred it
-may is not as simple especially if there are gaps or islands. Having an event
-specifically say it is the `END` of a chain will allow for UIs or systems to
-act accordingly based off the ending notation.
+may be embedded, `PATH`, `RELATION` and `END`. While `END` might be possible to
+infer, it may not be as simple especially if there are gaps or islands. Having
+an event specifically say it is the `END` of a chain will allow for UIs or
+systems to act accordingly based off the ending notation.
 
 ```json
 {

schemas/links/embeddedlinkend.json

@@ -5,10 +5,6 @@
       "END"
     ]
   },
-  "timestamp": {
-    "type": "string",
-    "format": "date-time"
-  },
   "from": {
     "description": "When consuming a CDEvent, you are consuming a parent event. So, when looking at the 'from' key, this is the parent's parent.",
     "type": "object",
@@ -29,8 +25,7 @@
   "additionalProperties": false,
   "type": "object",
   "required": [
-    "link_type",
-    "timestamp"
+    "link_type"
   ]
 }