diff --git a/schema/2.0/cyclonedx-2.0.schema.json b/schema/2.0/cyclonedx-2.0.schema.json
index 8e757386..79de8140 100644
--- a/schema/2.0/cyclonedx-2.0.schema.json
+++ b/schema/2.0/cyclonedx-2.0.schema.json
@@ -18,7 +18,7 @@
     "specFormat": {
       "type": "string",
       "title": "Specification Format",
-      "description": "Specifies the format. This value shall be \"CycloneDX\".",
+      "description": "Specifies the format. This value shall be `\"CycloneDX\"`.",
       "enum": [
         "CycloneDX"
       ]
@@ -43,7 +43,7 @@
     "version": {
       "type": "integer",
       "title": "BOM Version",
-      "description": "Whenever an existing BOM is modified, either manually or through automated processes, the version of the BOM SHOULD be incremented by 1. When a system is presented with multiple BOMs with identical serial numbers, the system SHOULD use the most recent version of the BOM. The default version is '1'.",
+      "description": "Whenever an existing BOM is modified, either manually or through automated processes, the version of the BOM SHOULD be incremented by 1. When a system is presented with multiple BOMs with identical serial numbers, the system SHOULD use the most recent version of the BOM. The default version is `1`.",
       "minimum": 1,
       "default": 1
     },
@@ -52,7 +52,7 @@
     },
     "components": {
       "$ref": "model/cyclonedx-component-2.0.schema.json#/$defs/components",
-      "description": "A collection of components. When a metadata component is present, this array represents the inventory of components associated with that subject, forming a bill of materials. When the metadata component is omitted, the array provides component data for interchange purposes without establishing a compositional relationship."
+      "description": "A collection of components. When a metadata component is present, this array represents the inventory of components associated with that subject, forming a bill of materials. When the `metadata.component` is omitted, the array provides component data for interchange purposes without establishing a compositional relationship."
     },
     "dependencies": {
       "$ref": "model/cyclonedx-dependency-2.0.schema.json#/$defs/dependencies"
diff --git a/schema/2.0/model/cyclonedx-ai-modelcard-2.0.schema.json b/schema/2.0/model/cyclonedx-ai-modelcard-2.0.schema.json
index 5bb06287..da31dfe7 100644
--- a/schema/2.0/model/cyclonedx-ai-modelcard-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-ai-modelcard-2.0.schema.json
@@ -9,7 +9,7 @@
       "$comment": "Model card support in CycloneDX is derived from TensorFlow Model Card Toolkit released under the Apache 2.0 license and available from https://github.com/tensorflow/model-card-toolkit/blob/main/model_card_toolkit/schema/v0.0.2/model_card.schema.json. In addition, CycloneDX model card support includes portions of VerifyML, also released under the Apache 2.0 license and available from https://github.com/cylynx/verifyml/blob/main/verifyml/model_card_toolkit/schema/v0.0.4/model_card.schema.json.",
       "type": "object",
       "title": "Model Card",
-      "description": "A model card describes the intended uses of a machine learning model and potential limitations, including biases and ethical considerations. Model cards typically contain the training parameters, which datasets were used to train the model, performance metrics, and other relevant data useful for ML transparency. This object SHOULD be specified for any component of type `machine-learning-model` and must not be specified for other component types.",
+      "description": "A model card describes the intended uses of a machine learning model and potential limitations, including biases and ethical considerations. Model cards typically contain the training parameters, which datasets were used to train the model, performance metrics, and other relevant data useful for ML transparency. This object SHOULD be specified for any component with `type=\"machine-learning-model\"` and must not be specified for other component types.",
       "additionalProperties": false,
       "properties": {
         "bom-ref": {
diff --git a/schema/2.0/model/cyclonedx-behavior-2.0.schema.json b/schema/2.0/model/cyclonedx-behavior-2.0.schema.json
index ca2b5ca2..25a7f194 100644
--- a/schema/2.0/model/cyclonedx-behavior-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-behavior-2.0.schema.json
@@ -266,7 +266,7 @@
           ],
           "meta:enum": {
             "activity": "An action that is performed, identified by a behavior, a behavior-instance reference, or a nested graph. The activity-flow counterpart of a step.",
-            "state": "A durable condition the subject rests in until a transition fires. The state-machine counterpart of a node. A composite state references its nested region through 'graph'.",
+            "state": "A durable condition the subject rests in until a transition fires. The state-machine counterpart of a node. A composite state references its nested region through `graph`.",
             "event": "An intermediate event that occurs during the graph.",
             "gateway": "A branch or merge point whose outgoing transitions carry the guards.",
             "initial": "The starting point of the graph or of a composite node.",
@@ -287,22 +287,22 @@
           "type": "integer",
           "title": "Ordinal",
           "minimum": 1,
-          "description": "Position within a sequential graph. Required when the graph ordering is 'sequential'. Ignored when transitions define the order."
+          "description": "Position within a sequential graph. Required when the graph's `ordering=\"sequential\"`. Ignored when transitions define the order."
         },
         "behavior": {
           "$ref": "../../behavior-taxonomy.schema.json",
           "title": "Behavior",
-          "description": "For an activity node, the behavior performed, drawn from the taxonomy. Mutually exclusive with 'ref' and 'graph'."
+          "description": "For an activity node, the behavior performed, drawn from the taxonomy. Mutually exclusive with `ref` and `graph`."
         },
         "ref": {
           "$ref": "cyclonedx-common-2.0.schema.json#/$defs/refLinkType",
           "title": "Behavior Reference",
-          "description": "For an activity node, a reference to a behavior instance. Mutually exclusive with 'behavior' and 'graph'."
+          "description": "For an activity node, a reference to a behavior instance. Mutually exclusive with `behavior` and `graph`."
         },
         "graph": {
           "$ref": "cyclonedx-common-2.0.schema.json#/$defs/refLinkType",
           "title": "Graph Reference",
-          "description": "A reference to a nested behavior graph. For an activity node it is the sub-process performed and is mutually exclusive with 'behavior' and 'ref'; for a composite node it is the nested region."
+          "description": "A reference to a nested behavior graph. For an activity node it is the sub-process performed and is mutually exclusive with `behavior` and `ref`; for a composite node it is the nested region."
         },
         "actors": {
           "type": "array",
diff --git a/schema/2.0/model/cyclonedx-blueprint-2.0.schema.json b/schema/2.0/model/cyclonedx-blueprint-2.0.schema.json
index 28a4937b..62c99dfc 100644
--- a/schema/2.0/model/cyclonedx-blueprint-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-blueprint-2.0.schema.json
@@ -283,11 +283,11 @@
           "items": {
             "$ref": "cyclonedx-party-2.0.schema.json#/$defs/partyChoice"
           },
-          "description": "The parties that created the blueprint. Each entry is either an inline party object or a reference to a previously declared party. The party's `roles` should include `author`."
+          "description": "The parties that created the blueprint. Each entry is either an inline party object or a reference to a previously declared party. The party's `roles` should include `\"author\"`."
         },
         "reviewer": {
           "$ref": "cyclonedx-party-2.0.schema.json#/$defs/partyChoice",
-          "description": "The party that reviewed the blueprint. The party's `roles` should include `reviewer`."
+          "description": "The party that reviewed the blueprint. The party's `roles` should include `\"reviewer\"`."
         },
         "reviewDate": {
           "type": "string",
@@ -297,7 +297,7 @@
         },
         "approver": {
           "$ref": "cyclonedx-party-2.0.schema.json#/$defs/partyChoice",
-          "description": "The party that approved the blueprint. The party's `roles` should include `signatory` or a custom role identifying the approving authority."
+          "description": "The party that approved the blueprint. The party's `roles` should include `\"signatory\"` or a custom role identifying the approving authority."
         },
         "approvalDate": {
           "type": "string",
@@ -338,7 +338,7 @@
           "type": "string",
           "title": "Review Frequency",
           "pattern": "^P(?!$)(\\d+Y)?(\\d+M)?(\\d+W)?(\\d+D)?$",
-          "description": "ISO 8601 duration for review frequency (e.g., P3M for quarterly)."
+          "description": "ISO 8601 duration for review frequency (e.g., `\"P3M\"` for quarterly)."
         }
       }
     },
@@ -410,7 +410,7 @@
         },
         "componentRef": {
           "$ref": "cyclonedx-common-2.0.schema.json#/$defs/refLinkType",
-          "description": "Reference using bom-link or bom-ref to the component this asset represents, including components of type `service`."
+          "description": "Reference using bom-link or bom-ref to the component this asset represents, including components of type `\"service\"`."
         },
         "partyRef": {
           "$ref": "cyclonedx-common-2.0.schema.json#/$defs/refLinkType",
@@ -844,7 +844,7 @@
           "items": {
             "$ref": "cyclonedx-party-2.0.schema.json#/$defs/partyChoice"
           },
-          "description": "Parties that own the dataset. Each entry is either an inline party object or a reference to a previously declared party. The party's `roles` should include `owner`."
+          "description": "Parties that own the dataset. Each entry is either an inline party object or a reference to a previously declared party. The party's `roles` should include `\"owner\"`."
         },
         "authorization": {
           "type": "array",
@@ -967,7 +967,7 @@
         },
         "dataFormat": {
           "type": "string",
-          "description": "Data format (e.g., JSON, XML, Protocol Buffers)."
+          "description": "Data format (e.g., `\"JSON\"`, `\"XML\"`, `\"Protocol Buffers\"`)."
         },
         "authentication": {
           "type": "array",
@@ -1727,7 +1727,7 @@
         },
         "owner": {
           "$ref": "cyclonedx-party-2.0.schema.json#/$defs/partyChoice",
-          "description": "The party responsible for tracking, validating, and maintaining this assumption over the lifecycle of the model. May be an inline party object or a reference to a previously declared party. The party's `roles` should include `owner`."
+          "description": "The party responsible for tracking, validating, and maintaining this assumption over the lifecycle of the model. May be an inline party object or a reference to a previously declared party. The party's `roles` should include `\"owner\"`."
         },
         "validationMethod": {
           "type": "string",
@@ -1943,7 +1943,7 @@
     "ownership": {
       "type": "array",
       "title": "Ownership",
-      "description": "Parties responsible for the asset. Each entry is either an inline party object or a reference to a previously declared party. The party's `roles` carry the relationship (`owner`, `steward`, `custodian`, `end-user`, or a custom role). Multiple parties may share the same role; preference among them is expressed via `role.order`.",
+      "description": "Parties responsible for the asset. Each entry is either an inline party object or a reference to a previously declared party. The party's `roles` carry the relationship (`\"owner\"`, `\"steward\"`, `\"custodian\"`, `\"end-user\"`, or a custom role). Multiple parties may share the same role; preference among them is expressed via `role.order`.",
       "uniqueItems": true,
       "items": {
         "$ref": "cyclonedx-party-2.0.schema.json#/$defs/partyChoice"
diff --git a/schema/2.0/model/cyclonedx-certification-2.0.schema.json b/schema/2.0/model/cyclonedx-certification-2.0.schema.json
index 05c08f0e..fcd2a179 100644
--- a/schema/2.0/model/cyclonedx-certification-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-certification-2.0.schema.json
@@ -60,7 +60,7 @@
         "jurisdiction": {
           "type": "string",
           "title": "Jurisdiction",
-          "description": "ISO 3166-1 alpha-2 country code, ISO 3166-2 subdivision, or supranational identifier such as `EU`, where the certification applies.",
+          "description": "ISO 3166-1 alpha-2 country code, ISO 3166-2 subdivision, or supranational identifier such as `\"EU\"`, where the certification applies.",
           "examples": [ "US", "EU", "GB", "AU", "US-CA" ]
         },
         "level": {
diff --git a/schema/2.0/model/cyclonedx-citation-2.0.schema.json b/schema/2.0/model/cyclonedx-citation-2.0.schema.json
index f917370c..7ea40c9a 100644
--- a/schema/2.0/model/cyclonedx-citation-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-citation-2.0.schema.json
@@ -31,7 +31,7 @@
           },
           "minItems": 1,
           "title": "Field References",
-          "description": "One or more [JSON Pointers](https://datatracker.ietf.org/doc/html/rfc6901) identifying the BOM fields to which the attribution applies.\nExactly one of the \"pointers\" or \"expressions\" elements must be present."
+          "description": "One or more [JSON Pointers](https://datatracker.ietf.org/doc/html/rfc6901) identifying the BOM fields to which the attribution applies.\nExactly one of the `pointers` or `expressions` elements must be present."
         },
         "expressions": {
           "type": "array",
@@ -42,7 +42,7 @@
           },
           "minItems": 1,
           "title": "Path Expressions",
-          "description": "One or more path expressions used to locate values within a BOM.\nExactly one of the \"pointers\" or \"expressions\" elements must be present."
+          "description": "One or more path expressions used to locate values within a BOM.\nExactly one of the `pointers` or `expressions` elements must be present."
         },
         "timestamp": {
           "type": "string",
@@ -53,12 +53,12 @@
         "attributedTo": {
           "$ref": "cyclonedx-common-2.0.schema.json#/$defs/refLinkType",
           "title": "Attributed To",
-          "description": "The `bom-ref` of an object, such as a component, service, tool, organisational entity, or person that supplied the cited information.\nAt least one of the \"attributedTo\" or \"process\" elements must be present."
+          "description": "The `bom-ref` of an object, such as a component, service, tool, organisational entity, or person that supplied the cited information.\nAt least one of the `attributedTo` or `process` elements must be present."
         },
         "process": {
           "$ref": "cyclonedx-common-2.0.schema.json#/$defs/refLinkType",
           "title": "Process Reference",
-          "description": "The `bom-ref` to a process (such as a formula, workflow, task, or step) defined in the `formulation` section that executed or generated the attributed data.\nAt least one of the \"attributedTo\" or \"process\" elements must be present."
+          "description": "The `bom-ref` to a process (such as a formula, workflow, task, or step) defined in the `formulation` section that executed or generated the attributed data.\nAt least one of the `attributedTo` or `process` elements must be present."
         },
         "note": {
           "type": "string",
diff --git a/schema/2.0/model/cyclonedx-common-2.0.schema.json b/schema/2.0/model/cyclonedx-common-2.0.schema.json
index 6e53d544..e8acf76a 100644
--- a/schema/2.0/model/cyclonedx-common-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-common-2.0.schema.json
@@ -259,7 +259,7 @@
             "support": "Community or commercial support",
             "source-distribution": "The location where the source code distributable can be obtained. This is often an archive format such as zip or tgz. The source-distribution type complements use of the version control (vcs) type.",
             "distribution": "Direct or repository download location",
-            "distribution-intake": "The location where a component was published to. This is often the same as \"distribution\" but may also include specialized publishing processes that act as an intermediary.",
+            "distribution-intake": "The location where a component was published to. This is often the same as `\"distribution\"` but may also include specialized publishing processes that act as an intermediary.",
             "license": "The reference to the license file. If a license URL has been defined in the license node, it should also be defined as an external reference for completeness.",
             "build-meta": "Build-system specific meta file (i.e. pom.xml, package.json, .nuspec, etc)",
             "build-system": "Reference to an automated build system",
@@ -285,7 +285,7 @@
             "certification-report": "Industry, regulatory, or other certification from an accredited (if applicable) certification body.",
             "codified-infrastructure": "Code or configuration that defines and provisions virtualized infrastructure, commonly referred to as Infrastructure as Code (IaC).",
             "quality-metrics": "Report or system in which quality metrics can be obtained.",
-            "poam": "Plans of Action and Milestones (POA&M) complement an \"attestation\" external reference. POA&M is defined by NIST as a \"document that identifies tasks needing to be accomplished. It details resources required to accomplish the elements of the plan, any milestones in meeting the tasks and scheduled completion dates for the milestones\".",
+            "poam": "Plans of Action and Milestones (POA&M) complement an `\"attestation\"` external reference. POA&M is defined by NIST as a \"document that identifies tasks needing to be accomplished. It details resources required to accomplish the elements of the plan, any milestones in meeting the tasks and scheduled completion dates for the milestones\".",
             "perspective": "A CycloneDX perspective defines a domain-specific view, enabling different audiences to interpret and navigate the data through their own conceptual lens.",
             "electronic-signature": "An e-signature is commonly a scanned representation of a written signature or a stylized script of the person's name.",
             "digital-signature": "A signature that leverages cryptography, typically public/private key pairs, which provides strong authenticity verification.",
@@ -294,7 +294,7 @@
             "patent-family": "References information about a patent family which may be defined in human-readable documents or in machine-readable formats such as CycloneDX or ST.96. A patent family is a group of related patent applications or granted patents that cover the same or similar invention. For detailed patent family information or to reference the information provided directly by patent offices, it is recommended to leverage standards from the World Intellectual Property Organization (WIPO) such as [ST.96](https://www.wipo.int/standards/en/st96).",
             "patent-assertion" : "References assertions made regarding patents associated with a component or service. Assertions distinguish between ownership, licensing, and other relevant interactions with patents.",
             "citation": "A reference to external citations applicable to the object identified by this BOM entry or the BOM itself. When used with a BOM-Link, this allows offloading citations into a separate CycloneDX BOM.",
-            "swid-tag": "A Software Identification (SWID) tag document conforming to ISO/IEC 19770-2. The reference resolves to the XML SoftwareIdentity document itself, including all of its metadata (entities, evidence, payload, links, and meta elements). This is distinct from the `swid` identifier scheme, which carries only the tagId of a SWID tag.",
+            "swid-tag": "A Software Identification (SWID) tag document conforming to ISO/IEC 19770-2. The reference resolves to the XML SoftwareIdentity document itself, including all of its metadata (entities, evidence, payload, links, and meta elements). This is distinct from the \"swid\" identifier scheme, which carries only the tagId of a SWID tag.",
             "gs1-digital-link": "A [GS1 Digital Link URI](https://ref.gs1.org/standards/digital-link/uri-syntax/) that connects the component's GS1 identification key, such as a GTIN, to online sources of information, including product data, safety documentation, digital product passports, and recall status. The URI may include key qualifiers, such as a batch or serial number, enabling identification at the class, batch, or individual item level. Component identity shall be derived from the component's identifiers, not from keys embedded in this URI.",
             "other": "Use this if no other types accurately describe the purpose of the external reference."
           }
@@ -531,7 +531,7 @@
         "distribution": {
           "type": "array",
           "title": "Origin Distribution",
-          "description": "The distribution of the origin across regions. The percentages of all entries shall total 100, within rounding of the stated precision.",
+          "description": "The distribution of the origin across regions. The percentages of all entries shall total `100`, within rounding of the stated precision.",
           "minItems": 1,
           "items": { "$ref": "#/$defs/originRegion" }
         }
@@ -547,14 +547,14 @@
         "isoCode": {
           "type": "string",
           "title": "ISO Code",
-          "description": "The country or subdivision of origin, expressed as an ISO 3166-1 alpha-2 country code (for example, 'CA' for Canada) or an ISO 3166-2 subdivision code (for example, 'US-CA' for California, United States).",
+          "description": "The country or subdivision of origin, expressed as an ISO 3166-1 alpha-2 country code (for example, 'CA' for Canada) or an ISO 3166-2 subdivision code (for example, `\"US-CA\"` for California, United States).",
           "pattern": "^[A-Z]{2}(-[A-Z0-9]{1,3})?$",
           "examples": [ "CA", "US-CA" ]
         },
         "percentage": {
           "type": "number",
           "title": "Percentage",
-          "description": "The percentage of the whole attributable to this region. The percentages of all entries in a distribution must total 100, within rounding of the stated precision.",
+          "description": "The percentage of the whole attributable to this region. The percentages of all entries in a distribution must total `100`, within rounding of the stated precision.",
           "minimum": 0,
           "maximum": 100
         },
@@ -597,7 +597,7 @@
     "extensibleProperties": {
       "type": "object",
       "title": "Extensible Properties",
-      "$comment": "This is a mixin. It intentionally does NOT restrict additional/unevaluated properties itself; schemas composing it via `allOf` are expected to close themselves with `unevaluatedProperties: false` so that both their own defined properties and these patternProperties remain usable.",
+      "$comment": "This is a mixin. It intentionally does NOT restrict additional/unevaluated properties itself; schemas composing it via `allOf` are expected to close themselves with `unevaluatedProperties=false` so that both their own defined properties and these patternProperties remain usable.",
       "patternProperties": {
         "^ext:[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,}:.+$": {
           "description": "CycloneDX supports a structured and namespace-aware mechanism for extensibility through the use of extensible properties. This mechanism enables organizations, ecosystems, and tool vendors to safely introduce custom properties without conflicting with the core schema or other extensions.\n\nExtensible properties are defined as a JSON object whose keys must conform to a strict pattern that resembles a reverse domain name structure, prefixed with ext:. This pattern provides a namespacing convention that aligns with well-established practices in other structured formats (e.g., XML namespaces).\n\nValues that are objects must declare the schema they conform to via `$schema`. This requirement applies recursively to objects contained in arrays, at any nesting depth.",
@@ -650,7 +650,7 @@
     "baseObject": {
       "type": "object",
       "description": "Base object for all CycloneDX entities. Automatically includes support for extensible properties.",
-      "$comment": "This is a mixin. It intentionally does NOT set `unevaluatedProperties: false` — that keyword cannot see properties defined by schemas composing this one via `allOf`, and would reject them. Concrete (leaf) schemas composing this mixin must close themselves with `unevaluatedProperties: false`.",
+      "$comment": "This is a mixin. It intentionally does NOT set `unevaluatedProperties=false` — that keyword cannot see properties defined by schemas composing this one via `allOf`, and would reject them. Concrete (leaf) schemas composing this mixin must close themselves with `unevaluatedProperties=false`.",
       "allOf": [
         { "$ref": "#/$defs/extensibleProperties" }
       ],
@@ -668,7 +668,7 @@
       "format": "date-time",
       "title": "Timestamp",
       "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(\\.\\d+)?Z$",
-      "description": "An RFC 3339-compliant UTC timestamp using Zulu time (i.e., ending with 'Z'). The format must be 'YYYY-MM-DDTHH:MM:SSZ' or include optional fractional seconds, e.g., 'YYYY-MM-DDTHH:MM:SS.sssZ'. Offsets such as '+00:00' are not allowed."
+      "description": "An RFC 3339-compliant UTC timestamp using Zulu time (i.e., ending with `\"Z\"`). The format must be `YYYY-MM-DDTHH:MM:SSZ` or include optional fractional seconds, e.g., `YYYY-MM-DDTHH:MM:SS.sssZ`. Offsets such as `\"+00:00\"` are not allowed."
     },
     "ordinalVersion": {
       "title": "Ordinal Version",
@@ -959,7 +959,7 @@
       "type": "string",
       "pattern": "^([a-z]{2})(-[A-Z]{2})?$",
       "title": "Locale",
-      "description": "Defines a syntax for representing two character language code (ISO-639) followed by an optional two character country code. The language code must be lower case. If the country code is specified, the country code must be upper case. The language code and country code must be separated by a minus sign. Examples: en, en-US, fr, fr-CA"
+      "description": "Defines a syntax for representing two character language code (ISO-639) followed by an optional two character country code. The language code must be lower case. If the country code is specified, the country code must be upper case. The language code and country code must be separated by a minus sign. Examples: `\"en\"`, `\"en-US\"`, `\"fr\"`, `\"fr-CA\"`."
     },
     "signatures": {
       "$ref": "cyclonedx-jss_X590_2023_10-2.0.schema.json#/$defs/signatures",
diff --git a/schema/2.0/model/cyclonedx-component-2.0.schema.json b/schema/2.0/model/cyclonedx-component-2.0.schema.json
index af1b29ef..1ffb6bef 100644
--- a/schema/2.0/model/cyclonedx-component-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-component-2.0.schema.json
@@ -46,14 +46,14 @@
             "container": "A packaging and/or runtime format, not specific to any particular technology, which isolates software inside the container from software outside of a container through virtualization technology. Refer to [https://en.wikipedia.org/wiki/OS-level_virtualization](https://en.wikipedia.org/wiki/OS-level_virtualization).",
             "platform": "A runtime environment that interprets or executes software. This may include runtimes such as those that execute bytecode, just-in-time compilers, interpreters, or low-code/no-code application platforms.",
             "operating-system": "A software operating system without regard to deployment model (i.e. installed on physical hardware, virtual machine, image, etc) Refer to [https://en.wikipedia.org/wiki/Operating_system](https://en.wikipedia.org/wiki/Operating_system).",
-            "device": "A hardware device such as a processor or chip-set. A hardware device containing firmware SHOULD include a component for the physical hardware itself and another component of type 'firmware' or 'operating-system' (whichever is relevant), describing information about the software running on the device. See also the list of [known device properties](https://github.com/CycloneDX/cyclonedx-property-taxonomy/blob/main/cdx/device.md).",
+            "device": "A hardware device such as a processor or chip-set. A hardware device containing firmware SHOULD include a component for the physical hardware itself and another component of `type=\"firmware\"` or `type=\"operating-system\"` (whichever is relevant), describing information about the software running on the device. See also the list of [known device properties](https://github.com/CycloneDX/cyclonedx-property-taxonomy/blob/main/cdx/device.md).",
             "device-driver": "A special type of software that operates or controls a particular type of device. Refer to [https://en.wikipedia.org/wiki/Device_driver](https://en.wikipedia.org/wiki/Device_driver).",
             "firmware": "A special type of software that provides low-level control over a device's hardware. Refer to [https://en.wikipedia.org/wiki/Firmware](https://en.wikipedia.org/wiki/Firmware).",
             "file": "A computer file. Refer to [https://en.wikipedia.org/wiki/Computer_file](https://en.wikipedia.org/wiki/Computer_file) for information about files.",
             "machine-learning-model": "A model based on training data that can make predictions or decisions without being explicitly programmed to do so.",
             "data": "A collection of discrete values that convey information.",
             "cryptographic-asset": "A cryptographic asset including algorithms, protocols, certificates, keys, tokens, and secrets.",
-            "material": "A physical substance in raw or processed form that is used to make, maintain, or repair an item, such as a metal, alloy, polymer, chemical, or other matter. Materials are commonly tracked for sourcing, provenance, and regulatory compliance. A finished physical item should be classified as 'device' instead.",
+            "material": "A physical substance in raw or processed form that is used to make, maintain, or repair an item, such as a metal, alloy, polymer, chemical, or other matter. Materials are commonly tracked for sourcing, provenance, and regulatory compliance. A finished physical item should be classified as 'type=\"device\"` instead.",
             "service": "A service, including microservices, function-as-a-service, and other types of network or intra-process services. Service-specific attributes, endpoints and the data profiles characterizing the data the service handles, apply exclusively to this component type."
           },
           "title": "Component Type",
@@ -91,23 +91,23 @@
         "name": {
           "type": "string",
           "title": "Component Name",
-          "description": "The name of the component. This will often be a shortened, single name of the component. Examples: commons-lang3 and jquery",
+          "description": "The name of the component. This will often be a shortened, single name of the component. Examples: `\"commons-lang3\"` and `\"jquery\"`.",
           "examples": ["tomcat-catalina"]
         },
         "version": {
           "$ref": "#/$defs/version",
           "title": "Component Version",
-          "description": "The component version. The version should ideally comply with semantic versioning but is not enforced.\nMust be used exclusively, either 'version' or 'versionRange', but not both."
+          "description": "The component version. The version should ideally comply with semantic versioning but is not enforced.\nMust be used exclusively, either `version` or `versionRange`, but not both."
         },
         "versionRange": {
           "$ref": "#/$defs/versionRange",
           "title": "Component Version Range",
-          "description": "For an external component, this specifies the accepted version range.\nThe value must adhere to the Package URL Version Range syntax (vers), as defined at <https://github.com/package-url/vers-spec\nMay only be used if `.isExternal` is set to `true`.\nMust be used exclusively, either 'version' or 'versionRange', but not both."
+          "description": "For an external component, this specifies the accepted version range.\nThe value must adhere to the Package URL Version Range syntax (vers), as defined at <https://github.com/package-url/vers-spec\nMay only be used if `isExternal=true`.\nMust be used exclusively, either `version` or 'versionRange', but not both."
         },
         "isExternal": {
           "type": "boolean",
           "title": "Component Is External",
-          "description": "Determine whether this component is external.\nAn external component is one that is not part of an assembly, but is expected to be provided by the environment, regardless of the component's `.scope`. This setting can be useful for distinguishing which components are bundled with the product and which can be relied upon to be present in the deployment environment.\nThis may be set to `true` for runtime components only. For `$.metadata.component`, it must be set to `false`.",
+          "description": "Determine whether this component is external.\nAn external component is one that is not part of an assembly, but is expected to be provided by the environment, regardless of the component's `scope`. This setting can be useful for distinguishing which components are bundled with the product and which can be relied upon to be present in the deployment environment.\nThis may be set to `true` for runtime components only. For `$.metadata.component`, it must be set to `false`.",
           "default": false
         },
         "description": {
@@ -124,11 +124,11 @@
           ],
           "meta:enum": {
             "required": "The component is required for runtime",
-            "optional": "The component is optional at runtime. Optional components are components that are not capable of being called due to them not being installed or otherwise accessible by any means. Components that are installed but due to configuration or other restrictions are prohibited from being called must be scoped as 'required'.",
+            "optional": "The component is optional at runtime. Optional components are components that are not capable of being called due to them not being installed or otherwise accessible by any means. Components that are installed but due to configuration or other restrictions are prohibited from being called must be scoped as `\"required\"`.",
             "excluded": "Components that are excluded provide the ability to document component usage for test and other non-runtime purposes. Excluded components are not reachable within a call graph at runtime."
           },
           "title": "Component Scope",
-          "description": "Specifies the scope of the component. If scope is not specified, 'required' scope SHOULD be assumed by the consumer of the BOM.",
+          "description": "Specifies the scope of the component. If scope is not specified, '\"required\"' scope SHOULD be assumed by the consumer of the BOM.",
           "default": "required"
         },
         "hashes": {
@@ -207,7 +207,7 @@
           "items": {"$ref": "#/$defs/componentOrChoice"},
           "uniqueItems": true,
           "title": "Components",
-          "description": "A list of components included in the parent component, including software, hardware, and services. Entries may be concrete components or component-choice wrappers expressing conditional or alternate relationships. This is not a dependency tree. It provides a way to specify a hierarchical representation of component assemblies, similar to system &#8594; subsystem &#8594; parts assembly in physical supply chains."
+          "description": "A list of components included in the parent component, including software, hardware, and services. Entries may be concrete components or component-choice wrappers expressing conditional or alternate relationships. This is not a dependency tree. It provides a way to specify a hierarchical representation of component assemblies, similar to system → subsystem → parts assembly in physical supply chains."
         },
         "evidence": {
           "$ref": "#/$defs/componentEvidence",
@@ -227,7 +227,7 @@
           "type": "array",
           "items": {"$ref": "#/$defs/componentData"},
           "title": "Data",
-          "description": "This object SHOULD be specified for any component of type `data` and must not be specified for other component types."
+          "description": "This object SHOULD be specified for any component with `type=\"data\"` and must not be specified for other component types."
         },
         "cryptoProperties": {
           "$ref": "cyclonedx-cryptography-2.0.schema.json#/$defs/cryptoProperties",
@@ -239,32 +239,32 @@
         "classification": {
           "$ref": "cyclonedx-physical-2.0.schema.json#/$defs/classification",
           "title": "Classification",
-          "description": "Hierarchical classification of the item, with optional taxonomy codes from external standards. This object may only be specified for components of type `device` or `material` and shall not be specified for other component types."
+          "description": "Hierarchical classification of the item, with optional taxonomy codes from external standards. This object may only be specified for components with `type=\"device\"` or `type=\"material\"` and shall not be specified for other component types."
         },
         "boardLocation": {
           "$ref": "cyclonedx-physical-2.0.schema.json#/$defs/boardLocation",
           "title": "Board Location",
-          "description": "Placement of the item on a printed circuit board, panel, or assembly. This object may only be specified for components of type `device` and shall not be specified for other component types."
+          "description": "Placement of the item on a printed circuit board, panel, or assembly. This object may only be specified for components with `type=\"device\"` and shall not be specified for other component types."
         },
         "deviceType": {
           "$ref": "cyclonedx-physical-2.0.schema.json#/$defs/deviceType",
           "title": "Device Type",
-          "description": "Package or mounting style of the physical item, expressed as a predefined device type or a custom device type. This object may only be specified for components of type `device` and shall not be specified for other component types."
+          "description": "Package or mounting style of the physical item, expressed as a predefined device type or a custom device type. This object may only be specified for components with `type=\"device\"` and shall not be specified for other component types."
         },
         "leadTime": {
           "$ref": "cyclonedx-physical-2.0.schema.json#/$defs/leadTime",
           "title": "Lead Time",
-          "description": "Supplier lead time for procuring the item. This object may only be specified for components of type `device` or `material` and shall not be specified for other component types."
+          "description": "Supplier lead time for procuring the item. This object may only be specified for components with `type=\"device\"` or `type=\"material\"` and shall not be specified for other component types."
         },
         "materialForm": {
           "$ref": "cyclonedx-physical-2.0.schema.json#/$defs/materialForm",
           "title": "Material Form",
-          "description": "Physical form in which the material is supplied, expressed as a predefined material form or a custom material form. This object may only be specified for components of type `material` and shall not be specified for other component types."
+          "description": "Physical form in which the material is supplied, expressed as a predefined material form or a custom material form. This object may only be specified for components with `type=\"material\"` and shall not be specified for other component types."
         },
         "quantity": {
           "$ref": "cyclonedx-physical-2.0.schema.json#/$defs/quantity",
           "title": "Quantity",
-          "description": "The quantity of the item in the context in which it is declared, such as the number of identical parts within the enclosing assembly or the amount of material in the described lot. This object may only be specified for components of type `device` or `material` and shall not be specified for other component types."
+          "description": "The quantity of the item in the context in which it is declared, such as the number of identical parts within the enclosing assembly or the amount of material in the described lot. This object may only be specified for components with `type=\"device\"` or `type=\"material\"` and shall not be specified for other component types."
         },
         "certifications": {
           "$ref": "cyclonedx-certification-2.0.schema.json#/$defs/certifications",
@@ -278,7 +278,7 @@
             "format": "iri-reference"
           },
           "title": "Endpoints",
-          "description": "The endpoint URIs of the service. Multiple endpoints are allowed. May only be used for components of type `service`.",
+          "description": "The endpoint URIs of the service. Multiple endpoints are allowed. May only be used for components with `type=\"service\"`.",
           "examples": ["https://example.com/api/v1/ticker"]
         },
         "dataProfiles": {
@@ -286,7 +286,7 @@
           "uniqueItems": true,
           "items": {"$ref": "cyclonedx-data-2.0.schema.json#/$defs/dataProfileChoice"},
           "title": "Data Profiles",
-          "description": "The data handled by the service, characterized by data profiles. Each entry is either an inline profile object or a reference using bom-link or bom-ref to a previously declared profile, typically declared in the root profiles catalogue. May only be used for components of type `service`. Data movement is intentionally not expressed here: flow direction, sources, destinations, authentication, and boundary crossings are modelled via blueprint flows, assets, and boundaries, which reference this component by bom-ref."
+          "description": "The data handled by the service, characterized by data profiles. Each entry is either an inline profile object or a reference using bom-link or bom-ref to a previously declared profile, typically declared in the root profiles catalogue. May only be used for components with `type=\"service\"`. Data movement is intentionally not expressed here: flow direction, sources, destinations, authentication, and boundary crossings are modelled via blueprint flows, assets, and boundaries, which reference this component by bom-ref."
         },
         "tags": {
           "$ref": "cyclonedx-common-2.0.schema.json#/$defs/tags",
@@ -311,7 +311,7 @@
           }
         },
         {
-          "description": "Requirement: 'versionRange' must not be present when 'isExternal' is `false`.",
+          "description": "Requirement: 'versionRange' must not be present when 'isExternal=false`.",
           "if": {
             "properties": { "isExternal": { "const": false } }
           },
@@ -321,7 +321,7 @@
           "else": true
         },
         {
-          "description": "Requirement: `classification`, `leadTime`, and `quantity` may only be present when `type` is `device` or `material`.",
+          "description": "Requirement: `classification`, `leadTime`, and `quantity` may only be present when `type=\"device\"` or `type=\"material\"`.",
           "if": {
             "properties": { "type": { "enum": ["device", "material"] } },
             "required": ["type"]
@@ -336,7 +336,7 @@
           }
         },
         {
-          "description": "Requirement: `boardLocation` and `deviceType` may only be present when `type` is `device`.",
+          "description": "Requirement: `boardLocation` and `deviceType` may only be present when `type=\"device\"`.",
           "if": {
             "properties": { "type": { "const": "device" } },
             "required": ["type"]
@@ -350,7 +350,7 @@
           }
         },
         {
-          "description": "Requirement: `materialForm` may only be present when `type` is `material`.",
+          "description": "Requirement: `materialForm` may only be present when `type=\"material\"`.",
           "if": {
             "properties": { "type": { "const": "material" } },
             "required": ["type"]
@@ -364,7 +364,7 @@
         },
         {
           "title": "Service Requirement",
-          "description": "Requirement: endpoints and dataProfiles may only be used for components of type `service`.",
+          "description": "Requirement: endpoints and dataProfiles may only be used for components with `type=\"service\"`.",
           "if": {
             "properties": { "type": { "const": "service" } }
           },
@@ -382,7 +382,7 @@
     },
     "componentOrChoice": {
       "title": "Component or Component Choice",
-      "description": "An entry in a components array. May be a concrete component, or a component-choice wrapper that expresses a conditional or alternate relationship between two or more components. The discriminator is the `type` property: when `type` is `component-choice`, the entry shall conform to the `componentChoice` schema; otherwise it shall conform to the `component` schema.",
+      "description": "An entry in a components array. May be a concrete component, or a component-choice wrapper that expresses a conditional or alternate relationship between two or more components. The discriminator is the `type` property: when `type=\"component-choice\"`, the entry shall conform to the `componentChoice` schema; otherwise it shall conform to the `component` schema.",
       "oneOf": [
         { "$ref": "#/$defs/component" },
         { "$ref": "#/$defs/componentChoice" }
@@ -403,7 +403,7 @@
           "type": "string",
           "const": "component-choice",
           "title": "Type",
-          "description": "Discriminator for a component-choice entry. The value shall be the literal string `component-choice`."
+          "description": "Discriminator for a component-choice entry. The value shall be the literal string `\"component-choice\"`."
         },
         "bom-ref": {
           "$ref": "cyclonedx-common-2.0.schema.json#/$defs/refType",
@@ -562,7 +562,7 @@
           "minimum": 0,
           "maximum": 1,
           "title": "Confidence",
-          "description": "The overall confidence of the detection from 0 to 1, where 1 is 100% confidence."
+          "description": "The overall confidence of the detection from `0` to `1`, where `1` is 100% confidence."
         },
         "methods": {
           "type": "array",
@@ -622,7 +622,7 @@
           "minimum": 0,
           "maximum": 1,
           "title": "Confidence",
-          "description": "The overall confidence of the detection from 0 to 1, where 1 is 100% confidence."
+          "description": "The overall confidence of the detection from `0` to `1`, where `1` is 100% confidence."
         },
         "methods": {
           "type": "array",
@@ -675,7 +675,7 @@
           "minimum": 0,
           "maximum": 1,
           "title": "Confidence",
-          "description": "The overall confidence of the evidence from 0 - 1, where 1 is 100% confidence."
+          "description": "The overall confidence of the evidence from `0` to `1`, where `1` is 100% confidence."
         },
         "concludedValue": {
           "type": "string",
@@ -808,12 +808,12 @@
         "configurationRef": {
           "$ref": "cyclonedx-common-2.0.schema.json#/$defs/refLinkType",
           "title": "Configuration Reference",
-          "description": "The bom-ref of the configuration that determines this component's configuration. Typically points to a component of type 'data' whose data type is 'configuration'."
+          "description": "The bom-ref of the configuration that determines this component's configuration. Typically points to a component with `type=\"data\"' whose `data.type=\"configuration\"`."
         },
         "changeMechanism": {
           "type": "array",
           "title": "Change Mechanism",
-          "description": "The step or steps required to apply a change to this component's configuration. When more than one value is present, all are required (for example, a software update followed by a restart). Values are roughly ordered from least to most disruptive. Use a single value of 'not-possible' when the configuration cannot be changed.",
+          "description": "The step or steps required to apply a change to this component's configuration. When more than one value is present, all are required (for example, a software update followed by a restart). Values are roughly ordered from least to most disruptive. Use a single value of `\"not-possible\"` when the configuration cannot be changed.",
           "uniqueItems": true,
           "items": {
             "type": "string",
diff --git a/schema/2.0/model/cyclonedx-composition-2.0.schema.json b/schema/2.0/model/cyclonedx-composition-2.0.schema.json
index 6ff555a1..33954809 100644
--- a/schema/2.0/model/cyclonedx-composition-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-composition-2.0.schema.json
@@ -86,7 +86,7 @@
         "incomplete_third_party_only": "The relationship is incomplete. Only relationships for third-party components, services, or their dependencies are represented.",
         "incomplete_third_party_proprietary_only": "The relationship is incomplete. Only relationships for third-party components, services, or their dependencies are represented, limited specifically to those that are proprietary.",
         "incomplete_third_party_opensource_only": "The relationship is incomplete. Only relationships for third-party components, services, or their dependencies are represented, limited specifically to those that are opensource.",
-        "unknown": "The relationship may be complete or incomplete. This usually signifies a 'best-effort' to obtain constituent components, services, or dependencies but the completeness is inconclusive.",
+        "unknown": "The relationship may be complete or incomplete. This usually signifies a \"best-effort\" to obtain constituent components, services, or dependencies but the completeness is inconclusive.",
         "not_specified": "The relationship completeness is not specified."
       }
     }
diff --git a/schema/2.0/model/cyclonedx-control-2.0.schema.json b/schema/2.0/model/cyclonedx-control-2.0.schema.json
index e7762a1e..e6c8fe0b 100644
--- a/schema/2.0/model/cyclonedx-control-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-control-2.0.schema.json
@@ -202,7 +202,7 @@
           "minimum": 0,
           "maximum": 1,
           "title": "Percentage",
-          "description": "Effectiveness as a decimal from 0 to 1."
+          "description": "Effectiveness as a decimal from `0` to `1`."
         },
         "rating": {
           "type": "string",
diff --git a/schema/2.0/model/cyclonedx-cryptography-2.0.schema.json b/schema/2.0/model/cyclonedx-cryptography-2.0.schema.json
index cb5c00f1..6640a7af 100644
--- a/schema/2.0/model/cyclonedx-cryptography-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-cryptography-2.0.schema.json
@@ -17,7 +17,7 @@
         "assetType": {
           "type": "string",
           "title": "Asset Type",
-          "description": "Cryptographic assets occur in several forms. Algorithms and protocols are most commonly implemented in specialized cryptographic libraries. They may, however, also be 'hardcoded' in software components. Certificates and related cryptographic material like keys, tokens, secrets or passwords are other cryptographic assets to be modelled.",
+          "description": "Cryptographic assets occur in several forms. Algorithms and protocols are most commonly implemented in specialized cryptographic libraries. They may, however, also be \"hardcoded\" in software components. Certificates and related cryptographic material like keys, tokens, secrets or passwords are other cryptographic assets to be modelled.",
           "enum": [
             "algorithm",
             "certificate",
@@ -40,7 +40,7 @@
             "primitive": {
               "type": "string",
               "title": "primitive",
-              "description": "Cryptographic building blocks used in higher-level cryptographic systems and protocols. Primitives represent different cryptographic routines: deterministic random bit generators (drbg, e.g. CTR_DRBG from NIST SP800-90A-r1), message authentication codes (mac, e.g. HMAC-SHA-256), blockciphers (e.g. AES), streamciphers (e.g. Salsa20), signatures (e.g. ECDSA), hash functions (e.g. SHA-256), public-key encryption schemes (pke, e.g. RSA), extended output functions (xof, e.g. SHAKE256), key derivation functions (e.g. pbkdf2), key agreement algorithms (e.g. ECDH), key encapsulation mechanisms (e.g. ML-KEM), authenticated encryption (ae, e.g. AES-GCM) and the combination of multiple algorithms (combiner, e.g. SP800-56Cr2).",
+              "description": "Cryptographic building blocks used in higher-level cryptographic systems and protocols. Primitives represent different cryptographic routines: deterministic random bit generators (`\"drbg\"`, e.g. CTR_DRBG from NIST SP800-90A-r1), message authentication codes (`\"mac\"`, e.g. HMAC-SHA-256), blockciphers (e.g. AES), streamciphers (e.g. Salsa20), signatures (e.g. ECDSA), hash functions (e.g. SHA-256), public-key encryption schemes (`\"pke`\", e.g. RSA), extended output functions (`\"xof\"`, e.g. SHAKE256), key derivation functions (e.g. pbkdf2), key agreement algorithms (e.g. ECDH), key encapsulation mechanisms (e.g. ML-KEM), authenticated encryption (`\"ae\"`, e.g. AES-GCM) and the combination of multiple algorithms (`\"combiner\"`, e.g. SP800-56Cr2).",
               "enum": [
                 "drbg",
                 "mac",
@@ -65,7 +65,7 @@
                 "block-cipher": "A block cipher is a symmetric key algorithm that operates on fixed-size blocks of data. It encrypts or decrypts the data in block units, providing confidentiality. Block ciphers are widely used in various cryptographic modes and protocols for secure data transmission.",
                 "stream-cipher": "A stream cipher is a symmetric key cipher where plaintext digits are combined with a pseudorandom cipher digit stream (keystream).",
                 "signature": "In cryptography, a signature is a digital representation of a message or data that proves its origin, identity, and integrity. Digital signatures are generated using cryptographic algorithms and are widely used for authentication and verification in secure communication.",
-                "hash": "A hash function is a mathematical algorithm that takes an input (or 'message') and produces a fixed-size string of characters, which is typically a hash value. Hash functions are commonly used in various cryptographic applications, including data integrity verification and password hashing.",
+                "hash": "A hash function is a mathematical algorithm that takes an input (or \"message\") and produces a fixed-size string of characters, which is typically a hash value. Hash functions are commonly used in various cryptographic applications, including data integrity verification and password hashing.",
                 "pke": "Public Key Encryption (PKE) is a type of encryption that uses a pair of public and private keys for secure communication. The public key is used for encryption, while the private key is used for decryption. PKE is a fundamental component of public-key cryptography.",
                 "xof": "An XOF is an extendable output function that can take arbitrary input and creates a stream of output, up to a limit determined by the size of the internal state of the hash function that underlies the XOF.",
                 "kdf": "A Key Derivation Function (KDF) derives key material from another source of entropy while preserving the entropy of the input.",
@@ -81,7 +81,7 @@
             "algorithmFamily": {
               "$ref": "../../cryptography-defs.schema.json#/definitions/algorithmFamiliesEnum",
               "title": "Algorithm Family",
-              "description": "A valid algorithm family identifier. If specified, this value shall be one of the enumeration of valid algorithm Family identifiers defined in the `cryptography-defs.schema.json` subschema.",
+              "description": "A valid algorithm family identifier. If specified, this value shall be one of the enumeration of valid algorithm Family identifiers defined in the \"cryptography-defs\" subschema.",
               "examples": [
                 "3DES",
                 "Blowfish",
@@ -91,12 +91,12 @@
             "parameterSetIdentifier": {
               "type": "string",
               "title": "Parameter Set Identifier",
-              "description": "An identifier for the parameter set of the cryptographic algorithm. Examples: in AES128, '128' identifies the key length in bits, in SHA256, '256' identifies the digest length, '128' in SHAKE128 identifies its maximum security level in bits, and 'SHA2-128s' identifies a parameter set used in SLH-DSA (FIPS205)."
+              "description": "An identifier for the parameter set of the cryptographic algorithm. Examples: in AES128, `\"128\"` identifies the key length in bits, in SHA256, `\"256\"` identifies the digest length, `\"128\"` in SHAKE128 identifies its maximum security level in bits, and `\"SHA2-128s\"` identifies a parameter set used in SLH-DSA (FIPS205)."
             },
             "ellipticCurve": {
               "$ref": "../../cryptography-defs.schema.json#/definitions/ellipticCurvesEnum",
               "title": "Elliptic Curve",
-              "description": "The specific underlying Elliptic Curve (EC) definition employed which is an indicator of the level of security strength, performance and complexity. If specified, this value shall be one of the enumeration of valid elliptic curves identifiers defined in the `cryptography-defs.schema.json` subschema."
+              "description": "The specific underlying Elliptic Curve (EC) definition employed which is an indicator of the level of security strength, performance and complexity. If specified, this value shall be one of the enumeration of valid elliptic curves identifiers defined in the \"cryptography-defs\" subschema."
             },
             "executionEnvironment": {
               "type": "string",
@@ -122,7 +122,7 @@
             "implementationPlatform": {
               "type": "array",
               "title": "Implementation platforms",
-              "description": "The target platforms for which the algorithm is implemented. The implementation can be 'generic', running on any platform or for a specific platform.",
+              "description": "The target platforms for which the algorithm is implemented. The implementation can be `\"generic\"`, running on any platform or for a specific platform.",
               "items": {
                 "type": "string",
                 "title": "Platform",
@@ -362,7 +362,7 @@
         "certificateProperties": {
           "type": "object",
           "title": "Certificate Properties",
-          "description": "Properties for cryptographic assets of asset type 'certificate'.",
+          "description": "Properties for cryptographic assets where `assetType=\"certificate\"`.",
           "additionalProperties": false,
           "properties": {
             "serialNumber": {
@@ -612,7 +612,7 @@
         "relatedCryptoMaterialProperties": {
           "type": "object",
           "title": "Related Cryptographic Material Properties",
-          "description": "Properties for cryptographic assets of asset type: `related-crypto-material`.",
+          "description": "Properties for cryptographic assets where `assetType=\"related-crypto-material\"`.",
           "additionalProperties": false,
           "properties": {
             "type": {
@@ -722,7 +722,7 @@
             "format": {
               "type": "string",
               "title": "Format",
-              "description": "The format of the related cryptographic material (e.g. P8, PEM, DER)."
+              "description": "The format of the related cryptographic material (e.g. `\"P8\"`, `\"PEM\"`, `\"DER\"`)."
             },
             "securedBy": {
               "$ref": "#/$defs/securedBy",
@@ -750,7 +750,7 @@
         "protocolProperties": {
           "type": "object",
           "title": "Protocol Properties",
-          "description": "Properties specific to cryptographic assets of type: `protocol`.",
+          "description": "Properties specific to cryptographic assets with `assetType=\"protocol\"`.",
           "additionalProperties": false,
           "properties": {
             "type": {
diff --git a/schema/2.0/model/cyclonedx-data-2.0.schema.json b/schema/2.0/model/cyclonedx-data-2.0.schema.json
index 8e342a29..e8560f12 100644
--- a/schema/2.0/model/cyclonedx-data-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-data-2.0.schema.json
@@ -337,7 +337,7 @@
         "format": {
           "type": "object",
           "title": "Format",
-          "description": "The serialisation or encoding format of this object, such as application/json, text/csv, or application/hl7-v2.",
+          "description": "The serialisation or encoding format of this object, such as `\"application/json\"`, `\"text/csv\"`, or `\"application/hl7-v2\"`.",
           "additionalProperties": false,
           "properties": {
             "url": {
@@ -596,7 +596,7 @@
         "party": {
           "$ref": "cyclonedx-party-2.0.schema.json#/$defs/party",
           "title": "Party",
-          "description": "An inline party object identifying the subject. Use this when the subject is best modelled as a party (organization, person, system, or persona) and has not been declared elsewhere in the document. The party's `roles` should include `data-subject`."
+          "description": "An inline party object identifying the subject. Use this when the subject is best modelled as a party (organization, person, system, or persona) and has not been declared elsewhere in the document. The party's `roles` should include `\"data-subject\"`."
         },
         "ref": {
           "$ref": "cyclonedx-common-2.0.schema.json#/$defs/refLinkType",
@@ -808,7 +808,7 @@
     "dataGovernance": {
       "type": "array",
       "title": "Data Governance",
-      "description": "Parties responsible for the data throughout its lifecycle. Each entry is either an inline party object or a reference to a previously declared party. The party's `roles` carry the governance relationship (`owner` for ownership and risk accountability, `steward` for content and business rules, `custodian` for safe custody, transport, and storage, `data-controller`, `data-processor`, `data-recipient`, or a custom role). Multiple parties may share the same role; preference among them is expressed via `role.order`.",
+      "description": "Parties responsible for the data throughout its lifecycle. Each entry is either an inline party object or a reference to a previously declared party. The party's `roles` carry the governance relationship (`\"owner\"` for ownership and risk accountability, `\"steward\"` for content and business rules, `\"custodian\"` for safe custody, transport, and storage, `\"data-controller\"`, `\"data-processor\"`, `\"data-recipient\"`, or a custom role). Multiple parties may share the same role; preference among them is expressed via `role.order`.",
       "uniqueItems": true,
       "items": {
         "$ref": "cyclonedx-party-2.0.schema.json#/$defs/partyChoice"
diff --git a/schema/2.0/model/cyclonedx-declaration-2.0.schema.json b/schema/2.0/model/cyclonedx-declaration-2.0.schema.json
index 951e5a80..4e3e998e 100644
--- a/schema/2.0/model/cyclonedx-declaration-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-declaration-2.0.schema.json
@@ -95,7 +95,7 @@
                           "minimum": 0,
                           "maximum": 1,
                           "title": "Score",
-                          "description": "The conformance of the claim between and inclusive of 0 and 1, where 1 is 100% conformance."
+                          "description": "The conformance of the claim between and inclusive of `0` and `1`, where `1` is 100% conformance."
                         },
                         "rationale": {
                           "type": "string",
@@ -121,7 +121,7 @@
                           "minimum": 0,
                           "maximum": 1,
                           "title": "Score",
-                          "description": "The confidence of the claim between and inclusive of 0 and 1, where 1 is 100% confidence."
+                          "description": "The confidence of the claim between and inclusive of `0` and `1`, where `1` is 100% confidence."
                         },
                         "rationale": {
                           "type": "string",
diff --git a/schema/2.0/model/cyclonedx-evidence-2.0.schema.json b/schema/2.0/model/cyclonedx-evidence-2.0.schema.json
index bfaf446e..46a89bda 100644
--- a/schema/2.0/model/cyclonedx-evidence-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-evidence-2.0.schema.json
@@ -179,7 +179,7 @@
           "minimum": 0,
           "maximum": 1,
           "title": "Confidence",
-          "description": "The confidence of the evidence from 0 to 1, where 1 is 100% confidence. Confidence is specific to the technique used. Each technique of analysis can have independent confidence."
+          "description": "The confidence of the evidence from `0` to `1`, where `1` is 100% confidence. Confidence is specific to the technique used. Each technique of analysis can have independent confidence."
         },
         "value": {
           "type": "string",
@@ -452,7 +452,7 @@
         "name": {
           "type": "string",
           "title": "Name",
-          "description": "The name or label of the data, for example 'attack prompt', 'model response', 'HTTP request', or 'scanner report'."
+          "description": "The name or label of the data, for example `\"attack prompt\"`, `\"model response\"`, `\"HTTP request\"`, or `\"scanner report\"`."
         },
         "ref": {
           "anyOf": [
diff --git a/schema/2.0/model/cyclonedx-formulation-2.0.schema.json b/schema/2.0/model/cyclonedx-formulation-2.0.schema.json
index 997dc6d9..86d8d216 100644
--- a/schema/2.0/model/cyclonedx-formulation-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-formulation-2.0.schema.json
@@ -133,7 +133,7 @@
         "inputs": {
           "title": "Inputs",
           "description": "Represents resources and data brought into a task at runtime by executor or task commands",
-          "examples": ["a `configuration` file which was declared as a local `component` or `externalReference`"],
+          "examples": ["a configuration file which was declared as a local `component` or `externalReference`"],
           "type": "array",
           "items": {
             "$ref": "#/$defs/inputType"
@@ -253,7 +253,7 @@
         "inputs": {
           "title": "Inputs",
           "description": "Represents resources and data brought into a task at runtime by executor or task commands",
-          "examples": ["a `configuration` file which was declared as a local `component` or `externalReference`"],
+          "examples": ["a configuration file which was declared as a local `component` or `externalReference`"],
           "type": "array",
           "items": {
             "$ref": "#/$defs/inputType"
@@ -560,7 +560,7 @@
         "inputs": {
           "title": "Inputs",
           "description": "Represents resources and data brought into a task at runtime by executor or task commands",
-          "examples": ["a `configuration` file which was declared as a local `component` or `externalReference`"],
+          "examples": ["a configuration file which was declared as a local `component` or `externalReference`"],
           "type": "array",
           "items": {
             "$ref": "#/$defs/inputType"
diff --git a/schema/2.0/model/cyclonedx-jss_X590_2023_10-2.0.schema.json b/schema/2.0/model/cyclonedx-jss_X590_2023_10-2.0.schema.json
index f1dcb7fc..24b23322 100644
--- a/schema/2.0/model/cyclonedx-jss_X590_2023_10-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-jss_X590_2023_10-2.0.schema.json
@@ -8,7 +8,7 @@
   "$defs": {
     "timestamp": {
       "title": "Timestamp",
-      "description": "An RFC 3339 timestamp in the UTC+0 time zone. Must use the 'Z' suffix. Sub-second precision, when present, MUST be exactly three digits (millisecond precision). If no sub-second digits are included, the decimal point MUST NOT be present. Matches the pattern: yyyy-mm-ddThh:mm:ss[.sss]Z",
+      "description": "An RFC 3339 timestamp in the UTC+0 time zone. Must use the `\"Z\"` suffix. Sub-second precision, when present, MUST be exactly three digits (millisecond precision). If no sub-second digits are included, the decimal point MUST NOT be present. Matches the pattern: `yyyy-mm-ddThh:mm:ss[.sss]Z`.",
       "$comment": "Normative source: ITU-T X.590 clause 6.1",
       "type": "string",
       "pattern": "^[0-9]{4}-(?:0[1-9]|1[0-2])-(?:0[1-9]|[12][0-9]|3[01])T(?:[01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9](?:\\.[0-9]+)?Z$",
@@ -21,7 +21,7 @@
         "withMilliseconds": {
           "$comment": "Internal helper for timestamp. Not part of the public schema API — do not reference externally; may change without notice.",
           "title": "Timestamp with Milliseconds",
-          "description": "An RFC 3339 timestamp in the UTC+0 time zone. Must use the 'Z' suffix. Sub-second precision MUST be exactly three digits (millisecond precision). Matches the pattern: yyyy-mm-ddThh:mm:ss.sssZ",
+          "description": "An RFC 3339 timestamp in the UTC+0 time zone. Must use the `\"Z\"` suffix. Sub-second precision MUST be exactly three digits (millisecond precision). Matches the pattern: `yyyy-mm-ddThh:mm:ss.sssZ`.",
           "type": "string",
           "pattern": "^[0-9]{4}-(?:0[1-9]|1[0-2])-(?:0[1-9]|[12][0-9]|3[01])T(?:[01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]\\.[0-9][0-9][0-9]Z$",
           "examples": [
@@ -33,7 +33,7 @@
     },
     "identifier": {
       "title": "Identifier",
-      "description": "A Universally Unique Identifier (UUID) conformant with RFC 4122. Used to uniquely identify a signature object. Signatures sharing the same 'id' are treated as versions of the same logical signature, differentiated by their 'modified' timestamp.",
+      "description": "A Universally Unique Identifier (UUID) conformant with RFC 4122. Used to uniquely identify a signature object. Signatures sharing the same `id` are treated as versions of the same logical signature, differentiated by their `modified` timestamp.",
       "$comment": "Normative source: ITU-T X.590 clause 6.1",
       "type": "string",
       "format": "uuid",
@@ -44,7 +44,7 @@
     },
     "hashAlgorithm": {
       "title": "Hash Algorithm",
-      "description": "This property identifies the hashing algorithm, as defined by the Internet Assigned Numbers Authority (IANA)…, that was used to hash the JCS version of the full JSON object (JSON Object + JSS Signature) and is a case-sensitive ASCII string. Implementations MAY use any current and widely accepted hashing algorithm (e.g., sha-256, sha-512) that is defined in the IANA registry. The actual signing process, defined in the algorithm property, sometimes uses an internal hashing algorithm inside the signing process itself, this property MAY identify the same hashing algorithm as the signing process or MAY identify a different hashing algorithm.",
+      "description": "This property identifies the hashing algorithm, as defined by the Internet Assigned Numbers Authority (IANA)…, that was used to hash the JCS version of the full JSON object (JSON Object + JSS Signature) and is a case-sensitive ASCII string. Implementations MAY use any current and widely accepted hashing algorithm (e.g., `\"sha-256\"`, `\"sha-512\"`) that is defined in the IANA registry. The actual signing process, defined in the algorithm property, sometimes uses an internal hashing algorithm inside the signing process itself, this property MAY identify the same hashing algorithm as the signing process or MAY identify a different hashing algorithm.",
       "$comment": "Normative source: ITU-T X.590 clause 6.2.1",
       "type": "string",
       "pattern": "^[a-z0-9-]+$",
@@ -144,7 +144,7 @@
     },
     "signatureObject": {
       "title": "Signature Object",
-      "description": "A JSS signature object as defined in ITU-T X.590 clause 6.2. Captures the hashing algorithm, signing algorithm, public key material (in one of four forms), the base64URL-encoded digital signature value, and optional metadata. May nest a child 'signature' property to form a counter-signature chain.",
+      "description": "A JSS signature object as defined in ITU-T X.590 clause 6.2. Captures the hashing algorithm, signing algorithm, public key material (in one of four forms), the base64URL-encoded digital signature value, and optional metadata. May nest a child `signature` property to form a counter-signature chain.",
       "$comment": "Normative source: ITU-T X.590 clauses 6.2 and 6.3",
       "type": "object",
       "properties": {
@@ -214,7 +214,7 @@
           "$ref": "#/$defs/timestamp/$defs/withMilliseconds",
           "title": "Modified Timestamp",
           "description": "The time that this particular version of the signature was last modified. The creator can use any time it deems most appropriate as the time that this version of the signature was modified, but it MUST be precise to the nearest millisecond (exactly three digits after the decimal place in seconds). The modified property MUST be later than or equal to the value of the created property. If the created and modified properties are the same, then this is the first version of the signature.",
-          "$comment": "Normative source: ITU-T X.590 clause 6.3.1. Cross-field invariant: 'modified' MUST be greater than or equal to 'created'. JSON Schema 2020-12 cannot compare two sibling property values, so this constraint is NOT enforced by this schema and MUST be validated by the consuming tool or conformance suite."
+          "$comment": "Normative source: ITU-T X.590 clause 6.3.1. Cross-field invariant: `modified` MUST be greater than or equal to `created`. JSON Schema 2020-12 cannot compare two sibling property values, so this constraint is NOT enforced by this schema and MUST be validated by the consuming tool or conformance suite."
         },
         "revoked": {
           "title": "Revoked Flag",
@@ -239,7 +239,7 @@
           "$ref": "#/$defs/timestamp",
           "title": "Valid Until",
           "description": "The time at which this signature is no longer considered valid. If the valid_until property is omitted, then there is no constraint on the latest time for which the signature is valid. This property MUST be greater than the timestamp in the valid_from property if the valid_from property is defined. If the revoked property is true then this property MUST be ignored.",
-          "$comment": "Normative source: ITU-T X.590 clause 6.3.1. Cross-field invariant: when 'valid_from' is present, 'valid_until' MUST be greater than 'valid_from'. JSON Schema 2020-12 cannot compare two sibling property values, so this constraint is NOT enforced by this schema and MUST be validated by the consuming tool or conformance suite."
+          "$comment": "Normative source: ITU-T X.590 clause 6.3.1. Cross-field invariant: when `valid_from` is present, `valid_until` MUST be greater than `valid_from`. JSON Schema 2020-12 cannot compare two sibling property values, so this constraint is NOT enforced by this schema and MUST be validated by the consuming tool or conformance suite."
         }
       },
       "required": ["hash_algorithm", "algorithm", "value"],
@@ -270,8 +270,8 @@
     },
     "signatures": {
       "title": "Signatures Array",
-      "description": "A JSON array of one or more signature objects. MUST be located at the top-level of the signed JSON object. The property name used to hold this array SHOULD be 'signatures', but implementations MAY use a different name provided it does not conflict with any other top-level property name in the host JSON object. All signature objects in this array are independent parallel signatures over the same JSON object; for chained counter-signatures, use the nested 'signature' property within an individual signature object.",
-      "$comment": "Normative source: ITU-T X.590 clause 6 – 'The property that holds the signature MUST be a JSON list property and MUST be located at the top-level of the original JSON object.'",
+      "description": "A JSON array of one or more signature objects. MUST be located at the top-level of the signed JSON object. The property name used to hold this array SHOULD be `signatures`, but implementations MAY use a different name provided it does not conflict with any other top-level property name in the host JSON object. All signature objects in this array are independent parallel signatures over the same JSON object; for chained counter-signatures, use the nested `signature` property within an individual signature object.",
+      "$comment": "Normative source: ITU-T X.590 clause 6 – \"The property that holds the signature MUST be a JSON list property and MUST be located at the top-level of the original JSON object.\"",
       "type": "array",
       "items": {
         "$ref": "#/$defs/signatureObject"
diff --git a/schema/2.0/model/cyclonedx-license-2.0.schema.json b/schema/2.0/model/cyclonedx-license-2.0.schema.json
index 2faa5543..93c2dd92 100644
--- a/schema/2.0/model/cyclonedx-license-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-license-2.0.schema.json
@@ -76,7 +76,7 @@
                     "url": {
                       "type": "string",
                       "title": "License URL",
-                      "description": "The URL to the license file. If specified, a 'license' externalReference should also be specified for completeness",
+                      "description": "The URL to the license file. If specified, a `externalReference` with `type=\"license\"` should also be specified for completeness",
                       "examples": [
                         "https://www.apache.org/licenses/LICENSE-2.0.txt"
                       ],
@@ -149,7 +149,7 @@
         "url": {
           "type": "string",
           "title": "License URL",
-          "description": "The URL to the license file. If specified, a 'license' externalReference should also be specified for completeness",
+          "description": "The URL to the license file. If specified, a `externalReference` with `type=\"license\"` should also be specified for completeness",
           "examples": ["https://www.apache.org/licenses/LICENSE-2.0.txt"],
           "format": "iri-reference"
         },
@@ -161,7 +161,7 @@
     },
     "licenseAcknowledgementEnumeration": {
       "title": "License Acknowledgement",
-      "description": "Declared licenses and concluded licenses represent two different stages in the licensing process within software development. Declared licenses refer to the initial intention of the software authors regarding the licensing terms under which their code is released. On the other hand, concluded licenses are the result of a comprehensive analysis of the project's codebase to identify and confirm the actual licenses of the components used, which may differ from the initially declared licenses. While declared licenses provide an upfront indication of the licensing intentions, concluded licenses offer a more thorough understanding of the actual licensing within a project, facilitating proper compliance and risk management. Observed licenses are defined in `@.evidence.licenses`. Observed licenses form the evidence necessary to substantiate a concluded license.",
+      "description": "Declared licenses and concluded licenses represent two different stages in the licensing process within software development. Declared licenses refer to the initial intention of the software authors regarding the licensing terms under which their code is released. On the other hand, concluded licenses are the result of a comprehensive analysis of the project's codebase to identify and confirm the actual licenses of the components used, which may differ from the initially declared licenses. While declared licenses provide an upfront indication of the licensing intentions, concluded licenses offer a more thorough understanding of the actual licensing within a project, facilitating proper compliance and risk management. Observed licenses are defined in `evidence.licenses`. Observed licenses form the evidence necessary to substantiate a concluded license.",
       "type": "string",
       "enum": [
         "declared",
diff --git a/schema/2.0/model/cyclonedx-metadata-2.0.schema.json b/schema/2.0/model/cyclonedx-metadata-2.0.schema.json
index 5da76761..b6fb5027 100644
--- a/schema/2.0/model/cyclonedx-metadata-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-metadata-2.0.schema.json
@@ -34,13 +34,13 @@
         },
         "manufacturer": {
           "title": "BOM Manufacturer",
-          "description": "The organization that created the BOM.\nManufacturer is common in BOMs created through automated processes. BOMs created through manual means may have `@.authors` instead.",
+          "description": "The organization that created the BOM.\nManufacturer is common in BOMs created through automated processes. BOMs created through manual means may have `authors` instead.",
           "$ref": "cyclonedx-common-2.0.schema.json#/$defs/organizationalEntity"
         },
         "authors": {
           "type": "array",
           "title": "BOM Authors",
-          "description": "The person(s) who created the BOM.\nAuthors are common in BOMs created through manual processes. BOMs created through automated means may have `@.manufacturer` instead.",
+          "description": "The person(s) who created the BOM.\nAuthors are common in BOMs created through manual processes. BOMs created through automated means may have `manufacturer` instead.",
           "items": {"$ref": "cyclonedx-common-2.0.schema.json#/$defs/organizationalContact"}
         },
         "component": {
@@ -79,7 +79,7 @@
     },
     "tlpClassification": {
       "title": "Traffic Light Protocol (TLP) Classification",
-      "description": "Traffic Light Protocol (TLP) is a classification system for identifying the potential risk associated with artefact, including whether it is subject to certain types of legal, financial, or technical threats. Refer to [https://www.first.org/tlp/](https://www.first.org/tlp/) for further information.\nThe default classification is \"CLEAR\"",
+      "description": "Traffic Light Protocol (TLP) is a classification system for identifying the potential risk associated with artefact, including whether it is subject to certain types of legal, financial, or technical threats. Refer to [https://www.first.org/tlp/](https://www.first.org/tlp/) for further information.\nThe default classification is `\"CLEAR\"`",
       "type" : "string",
       "default": "CLEAR",
       "enum": [
diff --git a/schema/2.0/model/cyclonedx-party-2.0.schema.json b/schema/2.0/model/cyclonedx-party-2.0.schema.json
index b38625c8..ab7d29d7 100644
--- a/schema/2.0/model/cyclonedx-party-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-party-2.0.schema.json
@@ -72,7 +72,7 @@
     "parties": {
       "type": "array",
       "title": "Parties",
-      "description": "Parties associated with the subject. Each item identifies an organization, individual, system, or abstract archetype playing one or more named roles such as manufacturer, supplier, author, integrator, quality-control, or any custom role. The same party can hold multiple roles, each independently ranked via `role.order` to express preference (for example, primary supplier with order 1 and alternate supplier with order 2). Items may be inline party objects or references to parties declared elsewhere.",
+      "description": "Parties associated with the subject. Each item identifies an organization, individual, system, or abstract archetype playing one or more named roles such as manufacturer, supplier, author, integrator, quality-control, or any custom role. The same party can hold multiple roles, each independently ranked via `role.order` to express preference (for example, primary supplier with order `1` and alternate supplier with order `2`). Items may be inline party objects or references to parties declared elsewhere.",
       "items": { "$ref": "#/$defs/partyChoice" }
     },
     "partyChoice": {
@@ -271,7 +271,7 @@
           "type": "integer",
           "minimum": 1,
           "title": "Order",
-          "description": "Preference order among parties sharing this role. Lower values indicate higher preference. Ties are permitted. Absence means unranked. For example, a primary supplier may have `order: 1` while an alternate supplier has `order: 2`.",
+          "description": "Preference order among parties sharing this role. Lower values indicate higher preference. Ties are permitted. Absence means unranked. For example, a primary supplier may have `order=1` while an alternate supplier has `order=2`.",
           "examples": [ 1, 2, 3 ]
         }
       }
@@ -357,7 +357,7 @@
               "name": {
                 "type": "string",
                 "title": "Name",
-                "description": "Label describing the URL, such as `homepage`, `support`, `press`, `status`, or `repository`.",
+                "description": "Label describing the URL, such as `\"homepage\"`, `\"support`, `\"press\"`, `\"status\"`, or `\"repository\"`.",
                 "examples": [ "homepage", "support", "press", "status", "repository" ]
               },
               "url": {
@@ -430,7 +430,7 @@
               "name": {
                 "type": "string",
                 "title": "Name",
-                "description": "Label describing the email, such as `work`, `personal`, `support`, or `security`.",
+                "description": "Label describing the email, such as `\"work\"`, `\"personal\"`, `\"support\"`, or `\"security\"`.",
                 "examples": [ "work", "personal", "support", "security" ]
               },
               "address": {
@@ -453,7 +453,7 @@
               "name": {
                 "type": "string",
                 "title": "Name",
-                "description": "Label describing the phone, such as `office`, `mobile`, `fax`, or `pager`.",
+                "description": "Label describing the phone, such as `\"office\"`, `\"mobile\"`, `\"fax\"`, or `\"pager\"`.",
                 "examples": [ "office", "mobile", "fax", "pager" ]
               },
               "number": {
@@ -476,7 +476,7 @@
               "name": {
                 "type": "string",
                 "title": "Name",
-                "description": "Label describing the URL, such as `homepage`, `github`, `linkedin`, `mastodon`, or `orcid`.",
+                "description": "Label describing the URL, such as `\"homepage\"`, `\"github\"`, `\"linkedin\"`, `\"mastodon\"`, or `\"orcid\"`.",
                 "examples": [ "homepage", "github", "linkedin", "orcid" ]
               },
               "url": {
@@ -535,7 +535,7 @@
                 "oracle":           "External data feed or oracle, including blockchain oracles that bridge off-chain data into on-chain systems.",
                 "smart-contract":   "On-chain program that executes deterministically.",
                 "device":           "Physical end user device such as a phone or IoT device acting as a party in its own right.",
-                "robot":            "Physical robot or autonomous mechanical system. For software-only counterparts, see `bot`, `agent`, or `automation`."
+                "robot":            "Physical robot or autonomous mechanical system. For software-only counterparts, see `\"bot\"`, `\"agent\"`, or `\"automation\"`."
               }
             },
             {
@@ -892,7 +892,7 @@
         "streetAddress": {
           "type": "string",
           "title": "Street Address",
-          "description": "The street address. Multi-line addresses are expressed as a single string with line breaks (`\\n`) between lines. Implementations and serialization formats are not required to preserve the order of elements in an array, so a multi-line address shall not be modeled as an array.",
+          "description": "The street address. Multi-line addresses are expressed as a single string with line breaks (`\"\\n\"`) between lines. Implementations and serialization formats are not required to preserve the order of elements in an array, so a multi-line address shall not be modeled as an array.",
           "examples": [
             "100 Main Street",
             "Acme Tower\nSuite 1200\n100 Main Street"
diff --git a/schema/2.0/model/cyclonedx-patent-2.0.schema.json b/schema/2.0/model/cyclonedx-patent-2.0.schema.json
index a9718078..071b982d 100644
--- a/schema/2.0/model/cyclonedx-patent-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-patent-2.0.schema.json
@@ -48,7 +48,7 @@
           "type": "string",
           "pattern": "^[A-Za-z0-9][A-Za-z0-9\\-/.()\\s]{0,28}[A-Za-z0-9]$",
           "title": "Patent Publication Number",
-          "description": "This is the number assigned to a patent application once it is published. Patent applications are generally published 18 months after filing (unless an applicant requests non-publication). This number is distinct from the application number. \n\nPurpose: Identifies the publicly available version of the application. \n\nFormat: Varies by jurisdiction, often similar to application numbers but includes an additional suffix indicating publication. \n\nExample:\n - US: US20240000123A1 (indicates the first publication of application US20240000123) \n - Europe: EP23123456A1 (first publication of European application EP23123456). \n\nWIPO ST.96 v8.0: \n - Publication Number field: https://www.wipo.int/standards/XMLSchema/ST96/V8_0/Patent/PublicationNumber.xsd"
+          "description": "This is the number assigned to a patent application once it is published. Patent applications are generally published 18 months after filing (unless an applicant requests non-publication). This number is distinct from the application number. \n\nPurpose: Identifies the publicly available version of the application. \n\nFormat: Varies by jurisdiction, often similar to application numbers but includes an additional suffix indicating publication. \n\nExample:\n - US: `\"US20240000123A1\"` (indicates the first publication of application US20240000123) \n - Europe: `\"EP23123456A1\"` (first publication of European application EP23123456). \n\nWIPO ST.96 v8.0: \n - Publication Number field: https://www.wipo.int/standards/XMLSchema/ST96/V8_0/Patent/PublicationNumber.xsd"
         },
         "title": {
           "type": "string",
diff --git a/schema/2.0/model/cyclonedx-perspective-2.0.schema.json b/schema/2.0/model/cyclonedx-perspective-2.0.schema.json
index 217cf587..207370a4 100644
--- a/schema/2.0/model/cyclonedx-perspective-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-perspective-2.0.schema.json
@@ -108,7 +108,7 @@
         "weight": {
           "type": "number",
           "title": "Weight",
-          "description": "Describes the importance of a field in relation to other fields. Values shall be between 0.0 and 1.0. This allows for relative ranking of mappings, where higher values indicate greater importance.",
+          "description": "Describes the importance of a field in relation to other fields. Values shall be between `0.0` and `1.0`. This allows for relative ranking of mappings, where higher values indicate greater importance.",
           "minimum": 0.0,
           "maximum": 1.0
         },
diff --git a/schema/2.0/model/cyclonedx-physical-2.0.schema.json b/schema/2.0/model/cyclonedx-physical-2.0.schema.json
index a9393184..6aff226b 100644
--- a/schema/2.0/model/cyclonedx-physical-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-physical-2.0.schema.json
@@ -15,12 +15,12 @@
           "type": "string",
           "minLength": 1,
           "title": "Category",
-          "description": "High-level category, such as `semiconductor`, `passive`, `connector`, `electromechanical`, or `optoelectronic`."
+          "description": "High-level category, such as `\"semiconductor\"`, `\"passive\"`, `\"connector\"`, `\"electromechanical\"`, or `\"optoelectronic\"`."
         },
         "subcategory": {
           "type": "string",
           "title": "Subcategory",
-          "description": "More specific classification within the category, such as `microcontroller`, `voltage-regulator`, or `ceramic-resonator`."
+          "description": "More specific classification within the category, such as `\"microcontroller\"`, `\"voltage-regulator\"`, or `\"ceramic-resonator\"`."
         },
         "codes": {
           "type": "array",
@@ -79,7 +79,7 @@
           "uniqueItems": true,
           "minItems": 1,
           "title": "Designators",
-          "description": "Reference designators identifying the placement on the assembly, such as U5, R12, C3.",
+          "description": "Reference designators identifying the placement on the assembly, such as `\"U5\"`, `\"R12\"`, `\"C3`\".",
           "examples": [ [ "U5" ], [ "C3", "C4", "C9", "C11", "C14", "C15" ] ]
         },
         "layer": {
diff --git a/schema/2.0/model/cyclonedx-release-notes-2.0.schema.json b/schema/2.0/model/cyclonedx-release-notes-2.0.schema.json
index b16f8e92..b1b91b80 100644
--- a/schema/2.0/model/cyclonedx-release-notes-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-release-notes-2.0.schema.json
@@ -87,7 +87,7 @@
         "pre-release",
         "internal"
       ],
-      "description": "The software versioning type. It is recommended that the release type use one of 'major', 'minor', 'patch', 'pre-release', or 'internal'. Representing all possible software release types is not practical, so standardizing on the recommended values, whenever possible, is strongly encouraged.\n\n* __major__ = A major release may contain significant changes or may introduce breaking changes.\n* __minor__ = A minor release, also known as an update, may contain a smaller number of changes than major releases.\n* __patch__ = Patch releases are typically unplanned and may resolve defects or important security issues.\n* __pre-release__ = A pre-release may include alpha, beta, or release candidates and typically have limited support. They provide the ability to preview a release prior to its general availability.\n* __internal__ = Internal releases are not for public consumption and are intended to be used exclusively by the project or manufacturer that produced it."
+      "description": "The software versioning type. It is recommended that the release type use one of `\"major\"`, `\"minor\"`, `\"patch\", `\"pre-release\"`, or `\"internal\"`. Representing all possible software release types is not practical, so standardizing on the recommended values, whenever possible, is strongly encouraged.\n\n* __major__ = A major release may contain significant changes or may introduce breaking changes.\n* __minor__ = A minor release, also known as an update, may contain a smaller number of changes than major releases.\n* __patch__ = Patch releases are typically unplanned and may resolve defects or important security issues.\n* __pre-release__ = A pre-release may include alpha, beta, or release candidates and typically have limited support. They provide the ability to preview a release prior to its general availability.\n* __internal__ = Internal releases are not for public consumption and are intended to be used exclusively by the project or manufacturer that produced it."
     },
     "note": {
       "type": "object",
@@ -101,7 +101,7 @@
         "locale": {
           "$ref": "cyclonedx-common-2.0.schema.json#/$defs/locale",
           "title": "Locale",
-          "description": "The ISO-639 (or higher) language code and optional ISO-3166 (or higher) country code. Examples include: \"en\", \"en-US\", \"fr\" and \"fr-CA\""
+          "description": "The ISO-639 (or higher) language code and optional ISO-3166 (or higher) country code. Examples include: `\"en\"`, `\"en-US\"`, `\"fr\"` and `\"fr-CA\"`."
         },
         "text": {
           "title": "Release note content",
diff --git a/schema/2.0/model/cyclonedx-requirement-2.0.schema.json b/schema/2.0/model/cyclonedx-requirement-2.0.schema.json
index d141b1b6..c3ff0f1e 100644
--- a/schema/2.0/model/cyclonedx-requirement-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-requirement-2.0.schema.json
@@ -29,7 +29,7 @@
         "id": {
           "type": "string",
           "title": "Identifier",
-          "description": "A unique identifier for the requirement, often used in requirement management systems (e.g., REQ-001)."
+          "description": "A unique identifier for the requirement, often used in requirement management systems (e.g., `\"REQ-001\"`)."
         },
         "name": {
           "type": "string",
diff --git a/schema/2.0/model/cyclonedx-risk-2.0.schema.json b/schema/2.0/model/cyclonedx-risk-2.0.schema.json
index b32be1e6..fd17c3ab 100644
--- a/schema/2.0/model/cyclonedx-risk-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-risk-2.0.schema.json
@@ -362,7 +362,7 @@
         },
         "owner": {
           "$ref": "cyclonedx-party-2.0.schema.json#/$defs/partyChoice",
-          "description": "The party accountable for this risk. May be an inline party object or a reference to a previously declared party. The party's `roles` should include `owner`."
+          "description": "The party accountable for this risk. May be an inline party object or a reference to a previously declared party. The party's `roles` should include `\"owner\"`."
         },
         "properties": {
           "$ref": "cyclonedx-common-2.0.schema.json#/$defs/properties"
@@ -372,7 +372,7 @@
     "rating": {
       "type": "object",
       "title": "Rating",
-      "description": "A methodology-neutral assessment of risk along likelihood and impact, with an overall score. The same shape expresses inherent, residual, and target risk so reductions can be compared. A rating can be qualitative (a `level`), semi-quantitative (a numeric `score` on a bounded scale), or quantitative (for example a probable monetary loss under [FAIR](https://www.fairinstitute.org/)). For a catalogue of assessment techniques, see [IEC 31010](https://www.iso.org/standard/72140.html).",
+      "description": "A methodology-neutral assessment of risk along likelihood and impact, with an overall score. The same shape expresses inherent, residual, and target risk so reductions can be compared. A rating can be qualitative (a `likelihood.level`), semi-quantitative (a numeric `score` on a bounded scale), or quantitative (for example a probable monetary loss under [FAIR](https://www.fairinstitute.org/)). For a catalogue of assessment techniques, see [IEC 31010](https://www.iso.org/standard/72140.html).",
       "additionalProperties": false,
       "properties": {
         "likelihood": {
@@ -406,7 +406,7 @@
           "minimum": 0,
           "maximum": 1,
           "title": "Confidence",
-          "description": "Confidence in this rating, expressed as a decimal from 0 to 1, where 1 is full confidence. Supports quantitative methods that reason over uncertainty."
+          "description": "Confidence in this rating, expressed as a decimal from `0` to `1`, where `1` is full confidence. Supports quantitative methods that reason over uncertainty."
         },
         "rationale": {
           "type": "string",
@@ -452,13 +452,13 @@
           "type": "number",
           "minimum": 0,
           "maximum": 1,
-          "description": "Probability as a decimal from 0 to 1."
+          "description": "Probability as a decimal from `0` to `1`."
         },
         "frequency": {
           "type": "number",
           "minimum": 0,
           "title": "Frequency",
-          "description": "The expected number of events within the timeframe, for frequency-based methods such as the [FAIR](https://www.fairinstitute.org/) loss event frequency. Unlike a probability, a frequency may exceed 1."
+          "description": "The expected number of events within the timeframe, for frequency-based methods such as the [FAIR](https://www.fairinstitute.org/) loss event frequency. Unlike a probability, a frequency may exceed `1`."
         },
         "timeframe": {
           "type": "string",
@@ -495,7 +495,7 @@
         "name": {
           "type": "string",
           "title": "Name",
-          "description": "The name of the likelihood factor being evaluated. Should clearly identify the dimension of likelihood being assessed, such as 'Threat Actor Capability', 'Exploit Availability', or 'Control Effectiveness'.",
+          "description": "The name of the likelihood factor being evaluated. Should clearly identify the dimension of likelihood being assessed, such as `\"Threat Actor Capability\"`, `\"Exploit Availability\"`, or `\"Control Effectiveness\"`.",
           "minLength": 1
         },
         "type": {
@@ -589,7 +589,7 @@
         "weight": {
           "type": "number",
           "title": "Weight",
-          "description": "The relative importance or weight of this factor in the overall likelihood calculation, expressed as a decimal between 0 and 1. When multiple factors are present, weights can be used to produce a weighted average likelihood score. A weight of 1 indicates full importance; a weight of 0 indicates no importance.",
+          "description": "The relative importance or weight of this factor in the overall likelihood calculation, expressed as a decimal between `0` and `1`. When multiple factors are present, weights can be used to produce a weighted average likelihood score. A weight of `1` indicates full importance; a weight of `0` indicates no importance.",
           "minimum": 0,
           "maximum": 1
         },
@@ -768,7 +768,7 @@
           "type": "string",
           "minLength": 1,
           "title": "Name",
-          "description": "The name of the impact factor being evaluated, such as 'Financial damage' or 'Reputation damage'."
+          "description": "The name of the impact factor being evaluated, such as `\"Financial damage\"` or `\"Reputation damage\"`."
         },
         "category": {
           "$ref": "#/$defs/impactCategory",
@@ -785,7 +785,7 @@
           "minimum": 0,
           "maximum": 1,
           "title": "Weight",
-          "description": "The relative importance of this factor in the overall impact calculation, expressed as a decimal from 0 to 1. OCTAVE Allegro, for example, ranks impact areas and multiplies the ranking by the factor value."
+          "description": "The relative importance of this factor in the overall impact calculation, expressed as a decimal from `0` to `1`. OCTAVE Allegro, for example, ranks impact areas and multiplies the ranking by the factor value."
         },
         "description": {
           "type": "string",
@@ -862,7 +862,7 @@
     "riskScore": {
       "type": "object",
       "title": "Risk Score",
-      "description": "The overall risk score, expressed as a qualitative `level`, a numeric `score`, or both, with `vector` and `methodology` recording how it was derived. The scale of `score` is defined by the methodology, since rating systems differ. For example, [OWASP Risk Rating](https://owasp.org/www-community/OWASP_Risk_Rating_Methodology) averages factors from 0 to 9, [DREAD](https://en.wikipedia.org/wiki/DREAD_%28risk_assessment_model%29) averages five 1 to 10 ratings, [FMEA](https://asq.org/quality-resources/fmea) multiplies three 1 to 10 axes into a 1 to 1000 risk priority number, and [FAIR](https://www.fairinstitute.org/) expresses probable loss in monetary terms.",
+      "description": "The overall risk score, expressed as a qualitative `level`, a numeric `score`, or both, with `vector` and `methodology` recording how it was derived. The scale of `score` is defined by the methodology, since rating systems differ. For example, [OWASP Risk Rating](https://owasp.org/www-community/OWASP_Risk_Rating_Methodology) averages factors from `0` to `9`, [DREAD](https://en.wikipedia.org/wiki/DREAD_%28risk_assessment_model%29) averages five `1` to `10` ratings, [FMEA](https://asq.org/quality-resources/fmea) multiplies three `1` to `10` axes into a `1` to `1000` risk priority number, and [FAIR](https://www.fairinstitute.org/) expresses probable loss in monetary terms.",
       "required": [
         "level"
       ],
@@ -912,13 +912,13 @@
                 "qualitative-matrix"
               ],
               "meta:enum": {
-                "dread": "[DREAD](https://en.wikipedia.org/wiki/DREAD_%28risk_assessment_model%29) risk rating model, the average of five ratings (damage, reproducibility, exploitability, affected users, discoverability) each scored 1 to 10.",
+                "dread": "[DREAD](https://en.wikipedia.org/wiki/DREAD_%28risk_assessment_model%29) risk rating model, the average of five ratings (damage, reproducibility, exploitability, affected users, discoverability) each scored `1` to `10`.",
                 "fair": "[Factor Analysis of Information Risk (FAIR)](https://www.fairinstitute.org/), a quantitative methodology expressing risk as loss event frequency multiplied by loss magnitude.",
                 "fmea": "[Failure Mode and Effects Analysis (FMEA)](https://asq.org/quality-resources/fmea), using a risk priority number of severity multiplied by occurrence multiplied by detection.",
                 "nist-sp-800-30": "[NIST SP 800-30](https://csrc.nist.gov/pubs/sp/800/30/r1/final) guide for conducting risk assessments, using its exemplary likelihood and impact scales.",
                 "octave": "[OCTAVE Allegro](https://www.sei.cmu.edu/documents/786/2007_005_001_14885.pdf), using its relative risk score.",
-                "owasp-risk-rating": "[OWASP Risk Rating](https://owasp.org/www-community/OWASP_Risk_Rating_Methodology), averaging likelihood and impact factors each scored 0 to 9.",
-                "qualitative-matrix": "A qualitative risk matrix that derives a risk level by plotting a likelihood band against an impact band, such as a five by five matrix producing a score from 1 to 25."
+                "owasp-risk-rating": "[OWASP Risk Rating](https://owasp.org/www-community/OWASP_Risk_Rating_Methodology), averaging likelihood and impact factors each scored `0` to `9`.",
+                "qualitative-matrix": "A qualitative risk matrix that derives a risk level by plotting a likelihood band against an impact band, such as a five by five matrix producing a score from `1` to `25`."
               }
             },
             {
@@ -1250,7 +1250,7 @@
           "items": {
             "$ref": "cyclonedx-party-2.0.schema.json#/$defs/partyChoice"
           },
-          "description": "The parties that performed the assessment. Each may be an inline party or a reference to a previously declared party, and may be a person or an automated system, agent, or tool. Automated assessors support continuous and automated assessment, as in a GRC engineering practice. A party's `roles` should include `auditor` or `assessor`."
+          "description": "The parties that performed the assessment. Each may be an inline party or a reference to a previously declared party, and may be a person or an automated system, agent, or tool. Automated assessors support continuous and automated assessment, as in a GRC engineering practice. A party's `roles` should include `\"auditor\"` or `\"assessor\"`."
         },
         "summary": {
           "type": "string",
diff --git a/schema/2.0/model/cyclonedx-threat-2.0.schema.json b/schema/2.0/model/cyclonedx-threat-2.0.schema.json
index edc8748c..f491dee0 100644
--- a/schema/2.0/model/cyclonedx-threat-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-threat-2.0.schema.json
@@ -908,7 +908,7 @@
         "operator": {
           "type": "string",
           "title": "Operator",
-          "description": "Specifies how the nodes listed in 'children' combine to achieve this node. A value of 'and' requires every child node; a value of 'or' requires any single child node. For example, a node whose children are a phishing node and a credential-stuffing node uses 'or' when either alone achieves it, or 'and' when both are needed together. A node with no children is a leaf and omits this property.",
+          "description": "Specifies how the nodes listed in `children` combine to achieve this node. A value of `\"and\"` requires every child node; a value of `\"or\"` requires any single child node. For example, a node whose children are a phishing node and a credential-stuffing node uses 'or' when either alone achieves it, or `\"and\"` when both are needed together. A node with no children is a leaf and omits this property.",
           "enum": [
             "and",
             "or"
diff --git a/schema/2.0/model/cyclonedx-usecase-2.0.schema.json b/schema/2.0/model/cyclonedx-usecase-2.0.schema.json
index 5d04372f..45dd0baf 100644
--- a/schema/2.0/model/cyclonedx-usecase-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-usecase-2.0.schema.json
@@ -31,7 +31,7 @@
           "type": "string",
           "title": "Name",
           "minLength": 1,
-          "description": "The name or title of the use case, typically expressed as a verb phrase that captures the goal from the actor's perspective (e.g., 'Place Order', 'Reset Password')."
+          "description": "The name or title of the use case, typically expressed as a verb phrase that captures the goal from the actor's perspective (e.g., `\"Place Order\"`, `\"Reset Password\"`)."
         },
         "description": {
           "type": "string",
@@ -147,13 +147,13 @@
           "type": "integer",
           "title": "Number",
           "minimum": 1,
-          "description": "The sequence number indicating the ordinal position of this step within its flow, starting at 1."
+          "description": "The sequence number indicating the ordinal position of this step within its flow, starting at `1`."
         },
         "description": {
           "type": "string",
           "title": "Description",
           "minLength": 1,
-          "description": "A clear, action-oriented statement describing what the actor does in this step and the expected system response, written in the form 'The [actor] [action]'."
+          "description": "A clear, action-oriented statement describing what the actor does in this step and the expected system response, written in the form `The [actor] [action]`."
         },
         "actor": {
           "$ref": "cyclonedx-common-2.0.schema.json#/$defs/refLinkType",
@@ -175,7 +175,7 @@
           "type": "string",
           "title": "Name",
           "minLength": 1,
-          "description": "A short, descriptive name identifying this alternative flow (e.g., 'Payment Declined', 'Guest Checkout')."
+          "description": "A short, descriptive name identifying this alternative flow (e.g., `\"Payment Declined\"`, `\"Guest Checkout\"`)."
         },
         "description": {
           "type": "string",
@@ -212,7 +212,7 @@
           "type": "string",
           "title": "Name",
           "minLength": 1,
-          "description": "A short, descriptive name identifying this exception scenario (e.g., 'Session Timeout', 'Insufficient Funds', 'Service Unavailable')."
+          "description": "A short, descriptive name identifying this exception scenario (e.g., `\"Session Timeout\"`, `\"Insufficient Funds\"`, `\"Service Unavailable\"`)."
         },
         "description": {
           "type": "string",
diff --git a/schema/2.0/model/cyclonedx-vulnerability-2.0.schema.json b/schema/2.0/model/cyclonedx-vulnerability-2.0.schema.json
index 42204323..6f90b6ca 100644
--- a/schema/2.0/model/cyclonedx-vulnerability-2.0.schema.json
+++ b/schema/2.0/model/cyclonedx-vulnerability-2.0.schema.json
@@ -258,7 +258,7 @@
         },
         "evidence": {
           "$ref": "#/$defs/vulnerabilityEvidence",
-          "description": "Evidence collected through extraction or analysis that substantiates the presence, absence, or exploitability of the vulnerability in the affected components. Evidence supports both positive determinations, such as a confirmed exploitable finding, and negative determinations, such as a `not_affected` conclusion, and complements the impact analysis and the proof of concept."
+          "description": "Evidence collected through extraction or analysis that substantiates the presence, absence, or exploitability of the vulnerability in the affected components. Evidence supports both positive determinations, such as a confirmed exploitable finding, and negative determinations, such as a `impactAnalysisState=\"not_affected\"` conclusion, and complements the impact analysis and the proof of concept."
         },
         "affects": {
           "type": "array",
@@ -499,7 +499,7 @@
       }
     },
     "affectedStatus": {
-      "description": "The vulnerability status of a given version or range of versions of a product. The statuses 'affected' and 'unaffected' indicate that the version is affected or unaffected by the vulnerability. The status 'unknown' indicates that it is unknown or unspecified whether the given version is affected. There can be many reasons for an 'unknown' status, including that an investigation has not been undertaken or that a vendor has not disclosed the status.",
+      "description": "The vulnerability status of a given version or range of versions of a product. The statuses `\"affected\"` and `\"unaffected\"` indicate that the version is affected or unaffected by the vulnerability. The status `\"unknown\"` indicates that it is unknown or unspecified whether the given version is affected. There can be many reasons for an `\"unknown\"` status, including that an investigation has not been undertaken or that a vendor has not disclosed the status.",
       "type": "string",
       "enum": [
         "affected",
@@ -592,7 +592,7 @@
           "minimum": 0,
           "maximum": 1,
           "title": "Confidence",
-          "description": "The overall confidence of the determination from 0 to 1, where 1 is 100% confidence."
+          "description": "The overall confidence of the determination from `0` to `1`, where `1` is 100% confidence."
         },
         "concludedValue": {
           "type": "string",