Remove {{glossary}} macros pointing to missing entries

caugner · caugner · commit c69edad063eb · 2026-05-11T19:14:04.000+02:00
diff --git a/files/en-us/glossary/rtp/index.md b/files/en-us/glossary/rtp/index.md
@@ -5,7 +5,7 @@ page-type: glossary-definition
 sidebar: glossarysidebar
 ---
 
-The **Real-time Transport Protocol** (**RTP**) is a network protocol which described how to transmit various media (audio, video) from one endpoint to another in a real-time fashion. RTP is suitable for video-streaming application, telephony over {{glossary("IP")}} like Skype and conference technologies.
+The **Real-time Transport Protocol** (**RTP**) is a network protocol which described how to transmit various media (audio, video) from one endpoint to another in a real-time fashion. RTP is suitable for video-streaming application, telephony over IP like Skype and conference technologies.
 
 The secure version of RTP, **SRTP**, is used by [WebRTC](/en-US/docs/Web/API/WebRTC_API), and uses encryption and authentication to minimize the risk of denial-of-service attacks and security breaches.
 
diff --git a/files/en-us/glossary/webassembly/index.md b/files/en-us/glossary/webassembly/index.md
@@ -5,7 +5,7 @@ page-type: glossary-definition
 sidebar: glossarysidebar
 ---
 
-**WebAssembly** (abbr. _Wasm_) is an open {{Glossary("binary")}} programming format that can be run in modern web {{Glossary("Browser", "browsers")}} in order to gain performance and/or provide new features for web pages.
+**WebAssembly** (abbr. _Wasm_) is an open binary programming format that can be run in modern web {{Glossary("Browser", "browsers")}} in order to gain performance and/or provide new features for web pages.
 
 ## See also
 
diff --git a/files/en-us/web/api/pbkdf2params/index.md b/files/en-us/web/api/pbkdf2params/index.md
@@ -25,7 +25,7 @@ The **`Pbkdf2Params`** dictionary of the [Web Crypto API](/en-US/docs/Web/API/We
 - `salt`
   - : An {{jsxref("ArrayBuffer")}}, a {{jsxref("TypedArray")}}, or a {{jsxref("DataView")}}. This should be a random or pseudo-random value of at least 16 bytes. Unlike the input key material passed into [`deriveKey()`](/en-US/docs/Web/API/SubtleCrypto/deriveKey), `salt` does not need to be kept secret.
 - `iterations`
-  - : A `Number` representing the number of times the hash function will be executed in `deriveKey()`. This determines how computationally expensive (that is, slow) the `deriveKey()` operation will be. In this context, slow is good, since it makes it more expensive for an attacker to run a {{Glossary("dictionary attack")}} against the keys. The general guidance here is to use as many iterations as possible, subject to keeping an acceptable level of performance for your application.
+  - : A `Number` representing the number of times the hash function will be executed in `deriveKey()`. This determines how computationally expensive (that is, slow) the `deriveKey()` operation will be. In this context, slow is good, since it makes it more expensive for an attacker to run a dictionary attack against the keys. The general guidance here is to use as many iterations as possible, subject to keeping an acceptable level of performance for your application.
 
 ## Examples
 
diff --git a/files/en-us/web/css/reference/properties/font-variant-ligatures/index.md b/files/en-us/web/css/reference/properties/font-variant-ligatures/index.md
@@ -7,7 +7,7 @@ browser-compat: css.properties.font-variant-ligatures
 sidebar: cssref
 ---
 
-The **`font-variant-ligatures`** [CSS](/en-US/docs/Web/CSS) property controls which {{Glossary("ligature", "ligatures")}} and {{Glossary("contextual forms")}} are used in the textual content of the elements it applies to. This leads to more harmonized forms in the resulting text.
+The **`font-variant-ligatures`** [CSS](/en-US/docs/Web/CSS) property controls which {{Glossary("ligature", "ligatures")}} and contextual forms are used in the textual content of the elements it applies to. This leads to more harmonized forms in the resulting text.
 
 {{InteractiveExample("CSS Demo: font-variant-ligatures")}}
 
diff --git a/files/en-us/web/security/authentication/federated_identity/index.md b/files/en-us/web/security/authentication/federated_identity/index.md
@@ -222,7 +222,7 @@ The specification also includes detailed recommendations for security practices
 Sign-out scenarios are more complex in a federated identity system than in a non-federated system, because:
 
 - The user might sign out of the RP either on the RP's site or on the IdP's site.
-- The user might choose to sign out of the RP only, or to sign out globally: that is, to sign out of all RPs that they are signed into with this IdP. This is a common requirement when we use federated identity to build a {{glossary("single sign-on", "single sign-on (SSO)")}} system, in which an employee might use a single set of corporate credentials to sign into email, a bug tracker, and a discussion forum.
+- The user might choose to sign out of the RP only, or to sign out globally: that is, to sign out of all RPs that they are signed into with this IdP. This is a common requirement when we use federated identity to build a single sign-on (SSO) system, in which an employee might use a single set of corporate credentials to sign into email, a bug tracker, and a discussion forum.
 
 Supporting these scenarios means implementing some communication mechanism between the RP and the IdP. For example:
 
diff --git a/files/en-us/web/security/authentication/index.md b/files/en-us/web/security/authentication/index.md
@@ -37,6 +37,6 @@ In this set of guides we'll describe the following authentication systems. Each
 
 ## Session management
 
-After a website has authenticated a user, the website will typically want to keep this user signed in without the need to reauthenticate, either for a limited time or even indefinitely until the user signs out. Websites typically accomplish this by setting a cookie that contains a secret session identifier, or using a {{glossary("digital signature", "cryptographically signed")}} object such as a {{glossary("JWT", JSON Web Token(JWT)"")}}.
+After a website has authenticated a user, the website will typically want to keep this user signed in without the need to reauthenticate, either for a limited time or even indefinitely until the user signs out. Websites typically accomplish this by setting a cookie that contains a secret session identifier, or using a {{glossary("digital signature", "cryptographically signed")}} object such as a JSON Web Token(JWT).
 
 In our [session management](/en-US/docs/Web/Security/Authentication/Session_management) guide, we outline session management best practices.
diff --git a/files/en-us/web/svg/reference/attribute/glyph-orientation-vertical/index.md b/files/en-us/web/svg/reference/attribute/glyph-orientation-vertical/index.md
@@ -52,7 +52,7 @@ You can use this attribute with the following SVG elements:
 </table>
 
 - `auto`
-  - : Fullwidth {{Glossary("ideographic")}} and fullwidth Latin text will be set with a glyph orientation of 0 degrees. Ideographic punctuation and other ideographic characters having alternate horizontal and vertical forms will use the vertical form of the glyph. Text which is not fullwidth will be set with a glyph orientation of 90 degrees.
+  - : Fullwidth ideographic and fullwidth Latin text will be set with a glyph orientation of 0 degrees. Ideographic punctuation and other ideographic characters having alternate horizontal and vertical forms will use the vertical form of the glyph. Text which is not fullwidth will be set with a glyph orientation of 90 degrees.
 
     This reorientation rule applies only to the first-level non-ideographic text. All further embedding of writing modes or bidirectional processing will be based on the first-level rotation.
 
diff --git a/files/en-us/web/svg/reference/attribute/href/index.md b/files/en-us/web/svg/reference/attribute/href/index.md
@@ -99,7 +99,7 @@ If the `href` attribute or the deprecated {{SVGAttr("xlink:href")}} attribute is
 
 Refer to the descriptions of the individual animation elements for any restrictions on what types of elements can be targets of particular types of animations.
 
-Except for any SVG-specific rules explicitly mentioned in this specification, the normative definition for this attribute is the {{Glossary("SMIL")}} Animation specification. In particular, see [SMIL Animation: Specifying the animation target](https://www.w3.org/TR/smil-animation/#SpecifyingAnimationTarget).
+Except for any SVG-specific rules explicitly mentioned in this specification, the normative definition for this attribute is the SMIL Animation specification. In particular, see [SMIL Animation: Specifying the animation target](https://www.w3.org/TR/smil-animation/#SpecifyingAnimationTarget).
 
 <table class="properties">
   <tbody>
