Fix typos

Author: taldromi

schema/v5.0/CVE_JSON_5.0_schema.json

@@ -252,7 +252,7 @@
                 },
                 "platforms": {
                     "title": "Platforms",
-                    "description": "List of specific platforms if the vulnerability is only relevant in the context of these platforms (optional). Platforms may include execution environments, operating systems, virtualization technolgies, hardware models, or computing architectures. Lack of this field or an empty array implies that the other fields are applicable for all relevant platforms.",
+                    "description": "List of specific platforms if the vulnerability is only relevant in the context of these platforms (optional). Platforms may include execution environments, operating systems, virtualization technologies, hardware models, or computing architectures. Lack of this field or an empty array implies that the other fields are applicable for all relevant platforms.",
                     "type": "array",
                     "minItems": 1,
                     "uniqueItems": true,
@@ -571,7 +571,7 @@
                 },
                 "replacedBy": {
                     "type": "array",
-                    "description": "Contains an array of CVE IDs that this CVE ID was rejected in favor of because the this CVE ID was assigned to the vulnerabilities.",
+                    "description": "Contains an array of CVE IDs that this CVE ID was rejected in favor of because this CVE ID was assigned to the vulnerabilities.",
                     "minItems": 1,
                     "uniqueItems": true,
                     "items": {
@@ -848,7 +848,7 @@
                 "properties": {
                     "format": {
                         "type": "string",
-                        "description": "Name of the score format. This provides a bit future proofing. Additional properties are not prohibitied, so this will support inclusion of proprietary formats. It also provides an easy future conversion mechanism when future score formats become part of the schema. example: cvssV4_4, format = 'cvssV4_4', other = cvssV4_4 json object. In the future the other properties can be converted to score properties when they become part of the schema.",
+                        "description": "Name of the score format. This provides a bit future proofing. Additional properties are not prohibited, so this will support inclusion of proprietary formats. It also provides an easy future conversion mechanism when future score formats become part of the schema. example: cvssV4_4, format = 'cvssV4_4', other = cvssV4_4 json object. In the future the other properties can be converted to score properties when they become part of the schema.",
                         "minLength": 1,
                         "maxLength": 64
                     },