diff --git a/docs/getting-started/glossary.mdx b/docs/getting-started/glossary.mdx
index 4481aab..01ed307 100644
--- a/docs/getting-started/glossary.mdx
+++ b/docs/getting-started/glossary.mdx
@@ -1,6 +1,7 @@
---
id: glossary
title: Glossary
+hide_table_of_contents: true
---
:::info
@@ -8,221 +9,312 @@ This glossary defines key terms used throughout the documentation and expands on
In case of a discrepancy, the C2PA specification takes precedence.
:::
-**Action**: An operation that an actor performs on an
+
+
+
+#### Action:
+
+An operation that an actor performs on an
asset. For example, "create," "embed," or "change contrast" for an image. See
[Assertions and actions](../manifest/writing/assertions-actions.md).
-**Active manifest**: The last in the list of
+#### Active manifest:
+
+The last in the list of
manifests inside of a manifest store. The active manifest has the set of content
bindings that can be validated. See [Working with
manifests](../manifest/understanding.md).
-**Actor**: A person, organization, device, or software
+#### Actor:
+
+A person, organization, device, or software
product. For example, a camera, image editing software, cloud service, or the
person using such tools.
-**Archive**: The serialized, portable representation
+#### Archive:
+
+The serialized, portable representation
of a working store saved to a file or stream (typically a `.c2pa` file). An
archive uses the standard JUMBF `application/c2pa` format and can be read back
to restore a `Builder`. While "working store" emphasizes the editable state,
"archive" emphasizes the saved bytes. See [Using working stores and
archives](../tasks/archives.mdx).
-**Assertion**: A data structure in the manifest that
+#### Assertion:
+
+A data structure in the manifest that
contains information about an asset's creation, authorship, how it's been
edited, and other relevant information. For a list of standard assertions, see
the [C2PA technical
specification](https://c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html).
See also [Assertions and actions](../manifest/writing/assertions-actions.md).
-**Asset**: A file or stream of data containing digital
+#### Asset:
+
+A file or stream of data containing digital
content. Currently, this means certain specific types of image, video, or audio
files, but the types of supported assets will expand in the future. See also
[composed asset](#composed-asset) and [derived asset](#derived-asset).
-**Asset metadata**: The portion of an asset
+#### Asset metadata:
+
+The portion of an asset
that represents non-technical information about the asset and its digital
content, as may be stored via standards such as Exif or XMP.
-**Asset rendition**: A representation of an
+#### Asset rendition:
+
+A representation of an
asset (either as a part of an asset or a completely new asset) where the digital
content has had a non-editorial transformation action (for example, re-encoding
or scaling) applied but where the asset metadata has not been modified.
-**Authenticity**: A property of digital content
+#### Authenticity:
+
+A property of digital content
comprising a set of facts (provenance data and hard bindings) that can be
cryptographically verified as not having been tampered with.
-**Builder**: A class in the SDK that you use to create
+#### Builder:
+
+A class in the SDK that you use to create
and add a signed manifest to an asset. See [Adding and signing a
manifest](../tasks/build.mdx), [Writing manifest
data](../manifest/writing/writing.md), and [Builder
reference](../manifest/json-ref/builder-ref.mdx).
-**Builder intent**: See [intent](#intent).
+#### Builder intent:
-**C2PA**: See [Coalition for Content Provenance and
-Authenticity](#coalition-for-content-provenance-and-authenticity).
+See [intent](#intent).
-**C2PA Tool**: Command-line utility for working with
+#### C2PA:
+
+See [Coalition for Content Provenance and
+Authenticity](#coalition-for-content-provenance-and-authenticity-c2pa).
+
+#### C2PA Tool:
+
+Command-line utility for working with
C2PA manifest data, implemented in the [c2pa-rs
repository](https://github.com/contentauth/c2pa-rs). The name of the utility is
"C2PA Tool," while the command to run the utility is `c2patool`. See [C2PA Tool
documentation](../c2patool/readme.md).
-**C2PA trust list**: A C2PA-managed list of
+#### C2PA trust list:
+
+A C2PA-managed list of
X.509 certificate trust anchors that issue certificates to hardware and software
signers that use them to sign claims. See [Trust
lists](../conformance/trust-lists.mdx).
-**C2PA TSA trust list**: A C2PA-managed
+#### C2PA TSA trust list:
+
+A C2PA-managed
list of X.509 certificate trust anchors that issue certificates to time-stamp
authorities (TSAs). See [Trust lists](../conformance/trust-lists.mdx).
-**CAI**: See [Content Authenticity
-Initiative](#content-authenticity-initiative).
+#### CAI:
+
+See [Content Authenticity
+Initiative](#content-authenticity-initiative-cai).
-**CAWG**: See [Creator Assertions Working Group](#creator-assertions-working-group).
+#### CAWG:
-**CAI open-source SDK**: Open-source
+See [Creator Assertions Working Group](#creator-assertions-working-group-cawg).
+
+#### CAI open-source SDK:
+
+Open-source
software for developing Content Credentials applications; includes the C2PA
Tool, Rust library, and libraries for Python, C/C++, web JavaScript, Node.js,
Android, and iOS. See [Introduction](../introduction.mdx).
-**CBOR**: See [Concise Binary Object
-Representation](#concise-binary-object-representation).
+#### CBOR:
+
+See [Concise Binary Object
+Representation](#concise-binary-object-representation-cbor).
-**Certificate**: An electronic document (also
+#### Certificate:
+
+An electronic document (also
called a public key certificate or digital certificate) that vouches for the
holder's identity. Like a passport, the certificate is issued by a trusted third
party (the certificate authority or CA), cannot be forged, and contains
identifying information. See [Signing and certificates](../signing/index.md).
-**Certificate authority (CA)**: A
+#### Certificate authority (CA):
+
+A
trusted third party that verifies the identity of an organization applying for a
digital certificate. After verifying the organization's identity, the CA issues
a certificate and binds the organization's identity to a public key. A digital
certificate can be trusted because it is chained to the CA's root certificate.
See [Getting a certificate](../signing/get-cert.md).
-**Claim**: Digitally signed and tamper-evident data in a
+#### Claim:
+
+Digitally signed and tamper-evident data in a
manifest that references a set of assertions by one or more actors, concerning
an asset, and the information necessary to represent the content binding. For
example, a claim could specify that a particular image was edited by John Doe
using Product X on 05/08/2021 at 11am to change the image contrast.
-**Claim generator**: The non-human (hardware
+#### Claim generator:
+
+The non-human (hardware
or software) actor that generates the claim about an asset as well as the claim
signature, thus leading to the asset's associated manifest.
-**Claim signature**: Part of the manifest that
+#### Claim signature:
+
+Part of the manifest that
is the digital signature on the claim using an actor's private key. See [Signing
and certificates](../signing/index.md).
-**Coalition for Content Provenance and Authenticity (C2PA)**: A formal coalition that drafts technical standards and specifications as
+#### Coalition for Content Provenance and Authenticity (C2PA):
+
+A formal coalition that drafts technical standards and specifications as
a foundation for universal content provenance. The C2PA is a mutually governed standards
development organization (SDO) under the structure of the Linux Foundation's Joint
Development Foundation. For more information, see [c2pa.org](https://c2pa.org).
-**Composed asset**: An asset created from
-multiple parts or fragments of digital content (referred to as ingredients). For
-example, an image (image A) with another image (image B) imported and
+#### Composed asset:
+
+An asset created from multiple parts or fragments of digital content (referred to as ingredients). For example, an image (image A) with another image (image B) imported and
superimposed on top of it. In this example, image B is referred to as an
ingredient. When starting from an existing asset, it's a special case of a
derived asset; however, a composed asset can also be created from a "blank
slate."
-**Concise Binary Object Representation (CBOR)**: A binary data serialization format loosely based on JSON that allows the
+#### Concise Binary Object Representation (CBOR):
+
+A binary data serialization format loosely based on JSON that allows the
transmission of data objects containing name-value pairs, but in a more concise
manner than with JSON. CBOR is defined in Internet Standard [RFC
8949](https://www.rfc-editor.org/rfc/rfc8949).
-**Content Authenticity Initiative (CAI)**: A group of creators, technologists, journalists, and activists leading the
+#### Content Authenticity Initiative (CAI):
+
+A group of creators, technologists, journalists, and activists leading the
global effort to address digital misinformation and content authenticity.
Collaborators include: Adobe, BBC, Microsoft, The New York Times Co., Leica,
Nikon, Truepic, and Qualcomm. For more information, see [Content Authenticity
Initiative](https://contentauthenticity.org).
-**Content binding**: Information that
+#### Content binding:
+
+Information that
associates specific digital content to a specific manifest associated with a
specific asset, either as a hard binding or a soft binding. See [Working with
manifests](../manifest/understanding.md).
-**Content Credentials**: Tamper-evident
+#### Content Credentials:
+
+Tamper-evident
metadata associated with an asset that shows the attribution and provenance
details for an asset. Corresponds to a manifest store. See [Working with
manifests](../manifest/understanding.md).
-**Context**: A class in the SDK that comprises
+#### Context:
+
+A class in the SDK that comprises
Settings and optionally a Signer, and that you pass to Reader or Builder to
control their behavior. See [Configuring SDK settings with
Context](../tasks/settings.mdx) and [Settings
reference](../manifest/json-ref/settings-ref.mdx).
-**ContextProvider**: An abstract base class
+#### ContextProvider:
+
+An abstract base class
in the SDK that defines the interface Reader and Builder use to access a
context.
-**Creator Assertions Working Group (CAWG)**: A working group within the Decentralized
+#### Creator Assertions Working Group (CAWG):
+
+A working group within the Decentralized
Identity Foundation (DIF) that defines technical standards for:
+
- [Identity assertions](#identity-assertion), proving who created content.
- Metadata assertions, providing detailed information about content.
- Training and data mining assertions, specifying how content may be used.
For details, see the [CAWG website](https://cawg.io/)
-**Cryptographic hash**: An algorithm that
+#### Cryptographic hash:
+
+An algorithm that
can be run on digital data such as an image file to produce a unique
"fingerprint" value. If the data changes then the hash value will also change.
-**Derived asset**: An asset created by starting
+#### Derived asset:
+
+An asset created by starting
from an existing asset and performing actions on it that modify its digital
content and asset metadata.
-**Digital content**: The portion of an asset
+#### Digital content:
+
+The portion of an asset
that represents the actual content, such as the pixels of an image, along with
any additional technical metadata required to understand the content (for
example, a color profile or encoding parameters).
-**Durable Content Credentials**:
+#### Durable Content Credentials:
+
An approach to help content provenance persist across content platforms by using
C2PA manifest data in conjunction with invisible watermarks, actively inserted
into the content, and content fingerprints, passively computed from the content.
See [Durable Content Credentials](../durable-cr/index.md).
-**Exchangeable image file format (Exif)**: A standard that specifies formats for images, sound, and ancillary tags used
+#### Exchangeable image file format (Exif):
+
+A standard that specifies formats for images, sound, and ancillary tags used
by digital cameras (including smartphones) and related devices.
-**Extensible Metadata Platform (XMP)**: An ISO standard, originally created by Adobe Inc., for the creation,
+#### Extensible Metadata Platform (XMP):
+
+An ISO standard, originally created by Adobe Inc., for the creation,
processing, and interchange of standardized and custom metadata for digital
documents and data sets. For more information, see [Adobe
XMP](https://www.adobe.com/products/xmp.html).
-**Fingerprint**: A set of inherent properties
+#### Fingerprint:
+
+A set of inherent properties
computable from digital content that identifies the content or near duplicates
of it. See [Watermarking and fingerprinting](../durable-cr/soft-bindings.mdx).
-**Hard binding**: One or more cryptographic
+#### Hard binding:
+
+One or more cryptographic
hashes that uniquely identifies an entire asset or a portion thereof.
-**Identity assertion**: A CAWG assertion
+#### Identity assertion:
+
+A CAWG assertion
that enables a credential holder to prove control over a digital identity and to
use that identity to document the named actor's role(s) in an asset's lifecycle.
See [CAWG - Identity Assertion](https://cawg.io/identity/) and [Reading CAWG
identity assertions](../manifest/reading/reading-cawg-id.md).
-**Identity claims aggregator**: An
+#### Identity claims aggregator:
+
+An
actor that collects CAWG identity claims (attestations) regarding a named actor
from various identity providers and can replay those identity claims into
identity assertions on behalf of the named actor. This may be the same as the
identity assertion generator.
-**Ingredient**: Part of a composed asset, such as
+#### Ingredient:
+
+Part of a composed asset, such as
an image superimposed on top of another image. See [Reading
ingredients](../manifest/reading/ingredients-reading.md) and [Writing
ingredients](../manifest/writing/ingredients.md).
-**Intent**: A declaration that tells a `Builder` what
+#### Intent:
+
+A declaration that tells a `Builder` what
kind of manifest to create. Intents enable validation, add actions required by
the C2PA specification, and help prevent invalid operations. There are three
intent types: **Create** for new digital creations (requires a
@@ -231,46 +323,70 @@ modifying a pre-existing parent asset (must have a parent ingredient), and
**Update** for non-editorial changes such as re-encoding (a restricted version
of Edit). See [Using builder intents](../tasks/intents.mdx).
-**Interim trust list**: Initial Content
+#### Interim trust list:
+
+Initial Content
Authenticity trust list that was frozen as of 1 Jan 2026. See [Trust
lists](../conformance/trust-lists.mdx).
-**Invisible watermark**: See
+#### Invisible watermark:
+
+See
[watermark](#watermark).
-**JSON (JavaScript Object Notation)**: A lightweight
+#### JSON (JavaScript Object Notation):
+
+A lightweight
data-interchange and file format that uses human-readable text to store and
transmit data objects consisting of attribute-value pairs and arrays (or other
serializable values). For more information, see [json.org](https://json.org).
-**JPEG universal metadata box format (JUMBF)**: An international technical
+#### JPEG universal metadata box format (JUMBF):
+
+An international technical
standard that provides a mechanism to embed and refer to generic metadata in JPEG files. See [ISO/IEC 19566](https://www.iso.org/standard/84635.html).
-**Manifest**: The set of information about the
+#### Manifest:
+
+The set of information about the
provenance of an asset based on the combination of one or more assertions
(including content bindings), a single claim, and a claim signature. A manifest
is part of a manifest store. See [Working with manifests](../manifest/understanding.md).
-**Manifest archive**: See [archive](#archive).
+#### Manifest archive:
+
+See [archive](#archive).
-**Manifest consumer**: An actor who consumes
+#### Manifest consumer:
+
+An actor who consumes
an asset with an associated manifest for the purpose of obtaining the provenance
data from the manifest.
-**Manifest repository**: A repository that
+#### Manifest repository:
+
+A repository that
contains manifests and manifest stores, and which can be searched using a
content binding.
-**Manifest store**: A collection of manifests
+#### Manifest store:
+
+A collection of manifests
that can either be embedded into an asset or be external to it. See [Working
with manifests](../manifest/understanding.md).
-**Manifest working store**: See
+#### Manifest working store:
+
+See
[working store](#working-store).
-**Metadata**: See [asset metadata](#asset-metadata).
+#### Metadata:
+
+See [asset metadata](#asset-metadata).
+
+#### Metadata assertion:
-**Metadata assertion**: A CAWG assertion
+A CAWG assertion
for binding metadata from standards such as XMP, IPTC, and Exif to a C2PA
manifest in a tamper-evident way. Unlike the `c2pa.metadata` assertion, it has no restrictions on which metadata fields may be included, so it supports a broader set of use cases. This
makes it well-suited for use in C2PA gathered assertions,
@@ -278,129 +394,182 @@ where the signer of the C2PA manifest does not attest to the accuracy of the
provided metadata but still ensures the integrity of the C2PA manifest. See
[CAWG - Metadata Assertion](https://cawg.io/metadata/).
-**Online Certificate Status Protocol (OCSP)**: An
+#### Online Certificate Status Protocol (OCSP):
+
+An
internet protocol used for obtaining the revocation status of an X.509 digital
certificate; that is, whether the certificate is still valid. See [IETF RFC
6960](https://www.rfc-editor.org/rfc/rfc6960).
-**Private key**: In public key cryptography, a
+#### Private key:
+
+In public key cryptography, a
unique digital key (very long number) used to decode messages that were
encrypted with the corresponding public key. Every private key matches to
exactly one public key and is the only key that can decode messages encoded by
the matching public key. To ensure security, a private key's owner must never
disclose it to anyone else.
-**Provenance**: The logical concept of
+#### Provenance:
+
+The logical concept of
understanding the history of an asset and its interaction with actors and other
assets, as represented by the provenance data.
-**Provenance data**: The set of manifests for
+#### Provenance data:
+
+The set of manifests for
an asset and, in the case of a composed asset, its ingredients.
-**Public key**: In public key cryptography, a
+#### Public key:
+
+In public key cryptography, a
unique digital key (very long number) used to encode messages that can then be
decrypted with the corresponding private key. Every public key matches to
exactly one private key. A message encoded using a particular public key can be
decoded only by using the matching private key. Public keys can be freely
disseminated without compromising security. See [Getting started - Introduction to public key infrastructure](index.mdx#introduction-to-public-key-infrastructure).
-**Reader**: A class in the SDK that you use to read and
+#### Reader:
+
+A class in the SDK that you use to read and
validate a manifest store from an asset. See [Reading and verifying manifest
data](../tasks/read.mdx), [Reading manifest
data](../manifest/reading/reading.md), and [Reader
reference](../manifest/json-ref/reader-ref.mdx).
-**Redaction**: Removing an assertion from an asset's
+#### Redaction:
+
+Removing an assertion from an asset's
manifest when the asset is used as an ingredient. See the [C2PA technical
specification](https://c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html).
-**Resource**: Binary assets referenced by manifest
+#### Resource:
+
+Binary assets referenced by manifest
assertions, such as thumbnails or ingredient thumbnails. See [Getting resources
from a manifest](../tasks/get-resources.mdx).
-**Settings**: A class in the SDK that controls
+#### Settings:
+
+A class in the SDK that controls
behavior such as thumbnail generation, trust lists, and verification flags. See
[Configuring SDK settings with Context](../tasks/settings.mdx) and [Settings
reference](../manifest/json-ref/settings-ref.mdx).
-**Sidecar file**: A file containing a manifest
+#### Sidecar file:
+
+A file containing a manifest
store, with the same base name as the asset file but with a `.c2pa` extension. A
sidecar file is an alternative to embedding the manifest store in an asset's
metadata. For example, an asset named `cat.jpg` would have a sidecar file named
`cat.c2pa`. See [Working with manifests](../manifest/understanding.md).
-**Signer**: An actor whose credential's private key is
+#### Signer:
+
+An actor whose credential's private key is
used to sign a claim. The signer is identified by the subject of the credential.
See [Signing and certificates](../signing/index.md).
-**Soft binding**: A content identifier that is
+#### Soft binding:
+
+A content identifier that is
either embedded as a watermark in the digital content or is not statistically
unique. For example, TrustMark watermarks are added via soft bindings. See
[Watermarking and fingerprinting](../durable-cr/soft-bindings.mdx).
-**Time-stamp**: A time-stamp issued by a trusted
+#### Time-stamp:
+
+A time-stamp issued by a trusted
time-stamp authority used to prove that a manifest signature existed at a
certain date and time. See [Trust lists](../conformance/trust-lists.mdx).
-**Time-stamp authority**: A trusted third
+#### Time-stamp authority:
+
+A trusted third
party that provides an [RFC
3161](https://www.rfc-editor.org/rfc/rfc3161)-compliant time-stamp authority
(TSA). See [RFC 3161, section
1](https://www.rfc-editor.org/rfc/rfc3161#section-1).
-**Training and data mining assertion**: A CAWG assertion that enables someone to provide information about whether an
+#### Training and data mining assertion:
+
+A CAWG assertion that enables someone to provide information about whether an
asset with C2PA metadata may be used for data mining or AI/ML training. See
[CAWG - Training and Data Mining
Assertion](https://cawg.io/training-and-data-mining/).
-**Trust list**: See [C2PA trust
+#### Trust list:
+
+See [C2PA trust
list](#c2pa-trust-list).
-**Trust signals**: The collection of information
+#### Trust signals:
+
+The collection of information
that can inform an actor's judgment of the trustworthiness of an asset. These
are in addition to the signer of a claim, upon which the fundamental trust model
relies.
-**TrustMark**: An open-source universal watermarking
+#### TrustMark:
+
+An open-source universal watermarking
system for images that several Adobe products use to make Durable Content
Credentials. See [TrustMark watermarking](../durable-cr/trustmark-intro.md).
-**TSA**: See [time-stamp
+#### TSA:
+
+See [time-stamp
authority](#time-stamp-authority).
-**Validation**: The process of determining if
+#### Validation:
+
+The process of determining if
Content Credentials are properly configured and signed. For example: Is an asset
actually the one described by its associated manifest, and does the manifest
follow the format and rules defined in the C2PA specification. See [Manifest
validation](../manifest/reading/validation.md).
-**Validator**: A manifest consumer who performs
+#### Validator:
+
+A manifest consumer who performs
validation on an active manifest. See [Manifest
validation](../manifest/reading/validation.md).
-**Verifiable credential (VC)**: A
+#### Verifiable credential (VC):
+
+A
tamper-evident credential whose authorship can be cryptographically verified.
This term may be used in the generic sense or may refer to the [W3C
Recommendation Verifiable Credentials Data
Model](https://www.w3.org/TR/vc-data-model-2.0/).
-**W3C decentralized identifier (DID)**:
+#### W3C decentralized identifier (DID):
+
A portable URL-based identifier associated with an entity used in a W3C verifiable credential. An example of a DID is `did:example:123456abcdef`. CAWG identity assertions use DIDs for [identity claims aggregation](#identity-claims-aggregator) credentials.
-**W3C decentralized identifier document**: Also referred to as a DID document, this is a document that is accessible using
+#### W3C decentralized identifier document:
+
+Also referred to as a DID document, this is a document that is accessible using
a verifiable data registry and contains information related to a specific W3C decentralized
identifier, such as the associated repository and public key information.
-**W3C verifiable credential**: A
+#### W3C verifiable credential:
+
+A
tamper-evident credential that has authorship that can be cryptographically
verified.
-**Watermark**: Information incorporated (perceptibly
+#### Watermark:
+
+Information incorporated (perceptibly
or imperceptibly) into the digital content of an asset which can be used, for
example, to uniquely identify the asset or to store a reference to a manifest.
See [Watermarking and fingerprinting](../durable-cr/soft-bindings.mdx).
-**Working store**: An editable, in-progress
+#### Working store:
+
+An editable, in-progress
manifest represented by a `Builder` that has not yet been signed and bound to an
asset. A working store contains the C2PA manifest state (claims, ingredients,
assertions) being assembled. It can be serialized to an archive for saving,
@@ -408,5 +577,10 @@ transferring, or resuming later, and uses the same standard JUMBF
`application/c2pa` format as signed manifests. See [Using working stores and
archives](../tasks/archives.mdx).
-**XMP**: See [Extensible Metadata
-Platform](#extensible-metadata-platform).
+#### XMP:
+
+See [Extensible Metadata
+Platform](#extensible-metadata-platform-xmp).
+
+
+
diff --git a/src/css/custom.css b/src/css/custom.css
index f593d02..adc5157 100644
--- a/src/css/custom.css
+++ b/src/css/custom.css
@@ -469,10 +469,53 @@ main .row:not(:has(.theme-doc-toc-desktop)) > .col {
*/
.scroll-target,
-.markdown span[id] {
+.markdown span[id],
+.markdown .glossary-inline-terms h4 {
scroll-margin-top: 130px; /* Slightly more than title bar */
}
+/* Glossary page: term labels use #### but should read like inline "Term: definition" blocks */
+.markdown .glossary-inline-terms > h4 {
+ display: inline;
+ font-size: inherit;
+ font-weight: var(--ifm-font-weight-bold);
+ line-height: inherit;
+ margin: 0;
+ padding: 0;
+ color: var(--ifm-heading-color);
+}
+
+/* Hash anchor link uses padding-left while invisible; that gap reads as extra space before the definition */
+.markdown .glossary-inline-terms > h4 .hash-link {
+ padding-left: 0;
+}
+
+.markdown .glossary-inline-terms > h4:focus .hash-link,
+.markdown .glossary-inline-terms > h4:hover .hash-link {
+ padding-left: 0.35rem;
+}
+
+.markdown .glossary-inline-terms > h4:not(:first-of-type)::before {
+ content: '';
+ display: block;
+ margin-top: var(--ifm-paragraph-margin-bottom);
+}
+
+.markdown .glossary-inline-terms > h4 + p {
+ display: inline;
+ margin: 0;
+}
+
+.markdown .glossary-inline-terms > h4 + p + p {
+ display: block;
+ margin: var(--ifm-paragraph-margin-bottom) 0;
+}
+
+.markdown .glossary-inline-terms > h4 + ul {
+ display: block;
+ margin: var(--ifm-paragraph-margin-bottom) 0;
+}
+
.warning {
background-color: rgb(250, 56, 62, 0.15);
padding: 0 10px;