opera-devtools-mcp 0.2.4 → 0.3.0

package/build/src/third_party/issue-descriptions/permissionElementUntrustedEvent.md

@@ -2,6 +2,6 @@
 
 The "{PLACEHOLDER_Type}" element can only be activated by actual user clicks, not simulated ones.
 
-To resolve this issue, do not use frameworks which simulate click events, (e.g. via `click()`) and do not prevent the `DOMActivate` event.
+To resolve this issue, don’t use frameworks which simulate click events, (e.g. via `click()`) and don’t stop the `DOMActivate` event.
 
 You can use the command line flag `--runtime-enabled-features=BypassPepcSecurityForTesting` to bypass this behavior for testing purposes.

package/build/src/third_party/issue-descriptions/placeholderDescriptionForInvisibleIssues.md

@@ -1,3 +1,3 @@
 # This is a placeholder issue description
 
-This description is used for issues that are not intended to be shown to the user. This means there is no need for a useful description.
+This description is used for issues that aren’t intended to be shown to the user. This means there is no need for a useful description.

package/build/src/third_party/issue-descriptions/selectElementAccessibilityDisallowedOptGroupChild.md

@@ -1,6 +1,6 @@
 # Invalid element or text node within <optgroup>
 
-An element which is not allowed in the content model of the `<optgroup>` element was found within an `<optgroup>` element. These elements will not consistently be accessible to people navigating by keyboard or using assistive technology.
+An element which isn’t allowed in the content model of the `<optgroup>` element was found within an `<optgroup>` element. These elements won’t consistently be accessible to people navigating by keyboard or using assistive technology.
 
 If using disallowed elements for layout structure and styling, consider using the allowed `<div>` element instead.
 

package/build/src/third_party/issue-descriptions/selectElementAccessibilityDisallowedSelectChild.md

@@ -1,6 +1,6 @@
 # Invalid element or text node within <select>
 
-An element which is not allowed in the content model of the `<select>` element was found within a `<select>` element. These elements will not consistently be accessible to people navigating by keyboard or using assistive technology.
+An element which isn’t allowed in the content model of the `<select>` element was found within a `<select>` element. These elements won’t consistently be accessible to people navigating by keyboard or using assistive technology.
 
 If using disallowed elements for layout structure and styling, consider using the allowed `<div>` element instead.
 

package/build/src/third_party/issue-descriptions/selectElementAccessibilityInteractiveContentAttributesSelectDescendant.md

@@ -1,3 +1,3 @@
 # Element with invalid attributes within a <select> element
 
-An element with `contenteditable` or `tabindex` attributes is not an allowed child of a `<select>` element. It will not consistently be accessible to people navigating by keyboard or using assistive technology.
+An element with `contenteditable` or `tabindex` attributes isn’t an allowed child of a `<select>` element. It won’t consistently be accessible to people navigating by keyboard or using assistive technology.

package/build/src/third_party/issue-descriptions/selectElementAccessibilityInteractiveContentLegendChild.md

@@ -1,3 +1,3 @@
 # Interactive element inside of a <legend> element
 
-An interactive element which is not allowed in the content model of the `<legend>` element was found within a `<legend>` element. Interactive elements are not allowed children of a `<legend>` element when used within an `<optgroup>` element. These elements will not consistently be accessible to people navigating by keyboard or using assistive technology.
+An interactive element which isn’t allowed in the content model of the `<legend>` element was found within a `<legend>` element. Interactive elements aren’t allowed children of a `<legend>` element when used within an `<optgroup>` element. These elements won’t consistently be accessible to people navigating by keyboard or using assistive technology.

package/build/src/third_party/issue-descriptions/selectElementAccessibilityInteractiveContentOptionChild.md

@@ -1,3 +1,3 @@
 # Interactive element inside of an <option> element
 
-An interactive element which is not allowed in the content model of the `<option>` element was found within an `<option>` element. These elements will not consistently be accessible to people navigating by keyboard or using assistive technology.
+An interactive element which isn’t allowed in the content model of the `<option>` element was found within an `<option>` element. These elements won’t consistently be accessible to people navigating by keyboard or using assistive technology.

package/build/src/third_party/issue-descriptions/selectElementAccessibilityNonPhrasingContentOptionChild.md

@@ -1,3 +1,3 @@
 # Non-phrasing content used within an <option> element
 
-The `<option>` element allows only non-interactive phrasing content, text, and `<div>` elements as its children. The semantics of non-phrasing content elements do not make sense as children of an `<option>`, and such semantics will largely be ignored by assistive technology since they are inappropriate in this context. Consider removing or changing such elements to one of the allowed phrasing content elements.
+The `<option>` element allows only non-interactive phrasing content, text, and `<div>` elements as its children. The semantics of non-phrasing content elements don’t make sense as children of an `<option>`, and such semantics will largely be ignored by assistive technology since they are inappropriate in this context. Consider removing or changing such elements to one of the allowed phrasing content elements.

package/build/src/third_party/issue-descriptions/selectivePermissionsIntervention.md

@@ -1,7 +1,7 @@
-# Selective Permissions Intervention
+# Selective permissions intervention
 
-The Selective Permissions Intervention blocks calls to privacy-sensitive APIs when they are called from ad scripts in order to align the permission grant with the user's intent. The particular API that was blocked, the call-stack that triggered the intervention, and why the script that called the API is considered ad-related is shown below.
+The Selective Permissions Intervention blocks calls to privacy-sensitive APIs when they are called from ad scripts to align the permission grant with the user’s intent. The particular API that was blocked, the call-stack that triggered the intervention, and why the script that called the API is considered ad-related is shown below.
 
 Note that Chrome considers any script with a URL that matches a rule in the [filterlist](ChromeFilterlistRepository) as ad script, and the matching rule is shown in the Ad Ancestry section. In addition, any script loaded while an ad script is in the JavaScript stack will also be considered an ad script by Chrome and is also shown in Ad Ancestry.
 
-If you believe this intervention  was in error (e.g., this call would occur even when loading the page with an ad blocker enabled), then please [file a bug](SelectivePermissionsInterventionIssue).
+If you believe this intervention was in error (e.g., this call would occur even when loading the page with an ad blocker enabled), then [file a bug](SelectivePermissionsInterventionIssue).

package/build/src/third_party/issue-descriptions/sharedArrayBuffer.md

@@ -2,6 +2,6 @@
 
 SharedArrayBuffers (SABs) can be used to construct high-resolution timers. High-resolution timers simplify Spectre attacks on cross-origin resources.
 
-To mitigate security risks across browsers, SharedArrayBuffers are gated behind cross-origin isolated contexts starting with Chrome 92 (July 2021). To continue using SharedArrayBuffers, please ensure that this page opts-into cross-origin isolation by setting Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy appropriately.
+To mitigate security risks across browsers, SharedArrayBuffers are gated behind cross-origin isolated contexts starting with Chrome 92 (July 2021). To continue using SharedArrayBuffers, ensure that this page opts-into cross-origin isolation by setting Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy appropriately.
 
 Note that for each iframe, only the first issue is reported for performance reasons.

package/build/src/third_party/issue-descriptions/sharedDictionaryUseErrorCrossOriginNoCorsRequest.md

@@ -1 +1 @@
-# Found a matching dictionary, but the dictionary can't be used for the cross origin no-cors request
+# Found a matching dictionary, but the dictionary can’t be used for the cross origin no-cors request

package/build/src/third_party/issue-descriptions/sharedDictionaryUseErrorMatchingDictionaryNotUsed.md

@@ -1,3 +1,3 @@
-# Found a matching dictionary, but the dictionary is not used for the response
+# Found a matching dictionary, but the dictionary isn’t used for the response
 
 Consider revisiting the `match` pattern or `match-dest` of the dictionary.

package/build/src/third_party/issue-descriptions/sharedDictionaryUseErrorUnexpectedContentDictionaryHeader.md

@@ -1 +1 @@
-# Can't decode the response because the header of dictionary compressed stream was not set correctly
+# Can’t decode the response because the header of dictionary compressed stream wasn’t set correctly

package/build/src/third_party/issue-descriptions/sharedDictionaryWriteErrorCossOriginNoCorsRequest.md

@@ -1 +1 @@
-# Can't register the cross origin response fetched by a no-cors request as as a dictionary
+# Can’t register the cross origin response fetched by a no-cors request as as a dictionary

package/build/src/third_party/issue-descriptions/sharedDictionaryWriteErrorDisallowedBySettings.md

@@ -1 +1 @@
-# Compression Dictionary is disabled by settings
+# compression dictionary is disabled by settings

package/build/src/third_party/issue-descriptions/sharedDictionaryWriteErrorExpiredResponse.md

@@ -1,3 +1,3 @@
-# The response can't be used as a dictionary because its freshness is expired
+# The response can’t be used as a dictionary because its freshness is expired
 
 Check `Cache-Control` and `Expires` headers.

package/build/src/third_party/issue-descriptions/sharedDictionaryWriteErrorFeatureDisabled.md

@@ -1,3 +1,3 @@
-# Compression Dictionary Transport feature is disabled
+# compression dictionary transport feature is disabled
 
-Please enable chrome://flags/#enable-compression-dictionary-transport
+enable chrome://flags/#enable-compression-dictionary-transport

package/build/src/third_party/issue-descriptions/sharedDictionaryWriteErrorInvalidStructuredHeader.md

@@ -1 +1 @@
-# `Use-As-Dictionary` HTTP response header is not a valid Structured Field value
+# `Use-As-Dictionary` HTTP response header isn’t a valid Structured Field Value

package/build/src/third_party/issue-descriptions/sharedDictionaryWriteErrorNavigationRequest.md

@@ -1,3 +1,3 @@
-# Can't register the response of the navigation request as a dictionary
+# Can’t register the response of the navigation request as a dictionary
 
-Navigation responses are not usable as compression dictionaries.
+Navigation responses aren’t usable as compression dictionaries.

package/build/src/third_party/issue-descriptions/sriInvalidSignatureHeader.md

@@ -1,9 +1,9 @@
-# A `signature` header is not formatted as a Structured Field Dictionary.
+# A `signature` header isn’t formatted as a Structured Field Dictionary
 
-Responses' [`signature`](signatureHeader) header should be formatted as a
-[Dictionary](sfDictionary) containing one or more signatures. Each member's key
+Responses’ [`signature`](signatureHeader) header should be formatted as a
+[Dictionary](sfDictionary) containing one or more signatures. Each member’s key
 is a label for the signature which maps it to the relevant metadata defined in
-a [`signature-input`](signatureInputHeader) header. Each member's value is a
+a [`signature-input`](signatureInputHeader) header. Each member’s value is a
 [Byte Sequence](sfByteSequence) containing the signature itself.
 
 For example, the following header contains a single Ed25519 signature labeled

package/build/src/third_party/issue-descriptions/sriInvalidSignatureInputHeader.md

@@ -1,10 +1,10 @@
-# A `signature-input` header is not formatted as a Structured Field Dictionary.
+# A `signature-input` header isn’t formatted as a Structured Field Dictionary
 
-Responses' [`signature-input`](signatureInputHeader) header should be formatted
+Responses’ [`signature-input`](signatureInputHeader) header should be formatted
 as a [Dictionary](sfDictionary) containing metadata regarding one or more
-signatures. Each member's key is a label for the metadata which maps it to the
+signatures. Each member’s key is a label for the metadata which maps it to the
 relevant signature defined in a [`signature`](signatureHeader) header. Each
-member's value is an [Inner List](sfInnerList) containing a set of components
+member’s value is an [Inner List](sfInnerList) containing a set of components
 over which a signature is generated. The list may have one or more parameters.
 
 For example, the following header contains metadata for a signature labeled

package/build/src/third_party/issue-descriptions/sriMissingSignatureHeader.md

@@ -1,4 +1,4 @@
-# A `signature-input` header was specified without an accompanying `signature` header.
+# A `signature-input` header was specified without an accompanying `signature` header
 
 [`signature-input`](signatureInputHeader) headers specify metadata that allows
 verification of signatures delivered with a response. If no

package/build/src/third_party/issue-descriptions/sriMissingSignatureInputHeader.md

@@ -1,7 +1,7 @@
-# A `signature` header was specified without an accompanying `signature-input` header.
+# A `signature` header was specified without an accompanying `signature-input` header
 
 [`signature`](signatureHeader) headers specify signatures which can be verified
-against a given response. Verification cannot proceed, however, in the absence of a
+against a given response. Verification can’t proceed, however, in the absence of a
 [`signature-input`](signatureInputHeader) header which defines relevant metadata
 which allows servers and clients to agree on the exact message which is being
 signed. Both headers must be present for verification to proceed.

package/build/src/third_party/issue-descriptions/sriSignatureHeaderValueIsIncorrectLength.md

@@ -1,7 +1,7 @@
-# A `signature` header contains a signature which cannot be verified.
+# A `signature` header contains a signature which can’t be verified
 
 This browser can only verify Ed25519 signatures, which are 512 bits long. The
-signature delivered with this response does not match that length.
+signature delivered with this response doesn’t match that length.
 
 For example, the following header contains a valid Ed25519 signature labeled
 "label":

package/build/src/third_party/issue-descriptions/sriSignatureHeaderValueIsNotByteSequence.md

@@ -1,9 +1,9 @@
-# A `signature` header member's value is not a Byte Sequence.
+# A `signature` header member’s value isn’t a Byte Sequence
 
-Responses' [`signature`](signatureHeader) header should be formatted as a
-[Dictionary](sfDictionary) containing one or more signatures. Each member's key
+Responses’ [`signature`](signatureHeader) header should be formatted as a
+[Dictionary](sfDictionary) containing one or more signatures. Each member’s key
 is a label for the signature which maps it to the relevant metadata defined in
-a [`signature-input`](signatureInputHeader) header. Each member's value is a
+a [`signature-input`](signatureInputHeader) header. Each member’s value is a
 [Byte Sequence](sfByteSequence) containing the signature itself.
 
 For example, the following header contains a single Ed25519 signature labeled

package/build/src/third_party/issue-descriptions/sriSignatureHeaderValueIsParameterized.md

@@ -1,9 +1,9 @@
-# A `signature` header member's value is parameterized.
+# A `signature` header member’s value is parameterized
 
-Responses' [`signature`](signatureHeader) header should be formatted as a
-[Dictionary](sfDictionary) containing one or more signatures. Each member's key
+Responses’ [`signature`](signatureHeader) header should be formatted as a
+[Dictionary](sfDictionary) containing one or more signatures. Each member’s key
 is a label for the signature which maps it to the relevant metadata defined in a
-[`signature-input`](signatureInputHeader) header. Each member's value is a
+[`signature-input`](signatureInputHeader) header. Each member’s value is a
 [Byte Sequence](sfByteSequence) containing the signature itself, with no
 additional parameters specified.
 

package/build/src/third_party/issue-descriptions/sriSignatureInputHeaderInvalidComponentName.md

@@ -1,4 +1,4 @@
-# A `signature-input` header member's value contains an unknown component.
+# A `signature-input` header member’s value contains an unknown component
 
 The metadata delivered via [`signature-input`](signatureInputHeader) can only
 contain a limited set of components in the list it specifies. The known

package/build/src/third_party/issue-descriptions/sriSignatureInputHeaderInvalidComponentType.md

@@ -1,6 +1,6 @@
-# A `signature-input` header's component is not a string.
+# A `signature-input` header’s component isn’t a string
 
-Responses' [`signature-input`](signatureInputHeader) header's members' values
+Responses’ [`signature-input`](signatureInputHeader) header’s members’ values
 are [Inner Lists](sfInnerList) whose contents are each strings. Perhaps you
 forgot double-quotes around a component?
 

package/build/src/third_party/issue-descriptions/sriSignatureInputHeaderInvalidDerivedComponentParameter.md

@@ -1,4 +1,4 @@
-# Invalid parameter on a derived component in a `signature-input` header.
+# Invalid parameter on a derived component in a `signature-input` header
 
 Derived components must be specified as deriving from the request, using the
 [`req` parameter](componentParameterReq). No other parameter may be specified.

package/build/src/third_party/issue-descriptions/sriSignatureInputHeaderInvalidHeaderComponentParameter.md

@@ -1,4 +1,4 @@
-# Invalid parameter on a header component in a `signature-input` header.
+# Invalid parameter on a header component in a `signature-input` header
 
 The header [`unencoded-digest`](unencodedDigestHeader) must be specified as
 being strictly serialized in the signature base, using the

package/build/src/third_party/issue-descriptions/sriSignatureInputHeaderInvalidParameter.md

@@ -1,6 +1,6 @@
-# Invalid parameter on the list of components in a `signature-input` header.
+# Invalid parameter on the list of components in a `signature-input` header
 
-The `signature-input` header's [Inner Lists](sfInnerList) must be specified with the
+The `signature-input` header’s [Inner Lists](sfInnerList) must be specified with the
 [`keyid` and `type` parameters](signatureParameters). The following parameters may
 also be specified:
 

package/build/src/third_party/issue-descriptions/sriSignatureInputHeaderKeyIdLength.md

@@ -1,10 +1,10 @@
-# Invalid `keyid` value in a `signature-input` header.
+# Invalid `keyid` value in a `signature-input` header
 
-The key specified in a [`signature-input`](signatureInputHeader) header's
-[`keyid` parameter](signatureParameters) is not a base64-encoded
-256 bit sequence, and therefore cannot be decoded as an Ed25519 public key.
+The key specified in a [`signature-input`](signatureInputHeader) header’s
+[`keyid` parameter](signatureParameters) isn’t a base64-encoded
+256 bit sequence, and therefore can’t be decoded as an Ed25519 public key.
 
-Note that the `keyid` parameter's value is a string, not a
+Note that the `keyid` parameter’s value is a string, not a
 [Byte Sequence](sfByteSequence). For example:
 
 ```

package/build/src/third_party/issue-descriptions/sriSignatureInputHeaderMissingLabel.md

@@ -1,6 +1,6 @@
-# Label mismatch between `signature` and `signature-input` headers.
+# Label mismatch between `signature` and `signature-input` headers
 
 A [`signature`](signatureHeader) header specifies a signature whose label does
 not appear in a corresponding [`signature-input`](signatureInputHeader) header.
-Without a `signature-input` header's definition of the signature's metadata,
-the signature cannot be verified.
+Without a `signature-input` header’s definition of the signature’s metadata,
+the signature can’t be verified.

package/build/src/third_party/issue-descriptions/sriSignatureInputHeaderMissingRequiredParameters.md

@@ -1,6 +1,6 @@
-# Missing a required parameter on the list of components in a `signature-input` header.
+# Missing a required parameter on the list of components in a `signature-input` header
 
-The [`signature-input`][signatureInputHeader] header's [Inner Lists](sfInnerList)
+The [`signature-input`][signatureInputHeader] header’s [Inner Lists](sfInnerList)
 must be specified with both the [`keyid` and `type` parameters](signatureParameters).
 
 ```

package/build/src/third_party/issue-descriptions/sriSignatureInputHeaderValueMissingComponents.md

@@ -1,6 +1,6 @@
-# Missing a required component in a `signature-input` header.
+# Missing a required component in a `signature-input` header
 
-The [`signature-input`](signatureInputHeader) header's
+The [`signature-input`](signatureInputHeader) header’s
 [Inner Lists](sfInnerList) must contain the string "`unencoded-digest`" with an
 `sf` parameter:
 

package/build/src/third_party/issue-descriptions/sriSignatureInputHeaderValueNotInnerList.md

@@ -1,6 +1,6 @@
-# A `signature-input` header has a member whose value is not an Inner List.
+# A `signature-input` header has a member whose value isn’t an Inner List
 
-The value of each member of a [`signature-input`](signatureInputHeader) header's
+The value of each member of a [`signature-input`](signatureInputHeader) header’s
 [Dictionary][sfDictionary] must be an [Inner List](sfInnerList) containing the
 set of components over which a signature is generated.
 

package/build/src/third_party/issue-descriptions/sriValidationFailedIntegrityMismatch.md

@@ -1,10 +1,10 @@
-# Integrity verification failed.
+# Integrity verification failed
 
 The signature associated with a response could be successfully verified, but the
 public keys asserted in the [`signature-input`](signatureInputHeader)
-header's [`keyid` parameter](signatureParameters) do not match the integrity
-assertions made by the request's initiator. Verificiation failed.
+header’s [`keyid` parameter](signatureParameters) don’t match the integrity
+assertions made by the request’s initiator. Verification failed.
 
-The following are the keys specified by the request's initiator:
+The following are the keys specified by the request’s initiator:
 
 {PLACEHOLDER_integrityAssertions}

package/build/src/third_party/issue-descriptions/sriValidationFailedInvalidLength.md

@@ -1,5 +1,5 @@
-# Signature verification failed: the signature provided is not an Ed25519 signature.
+# Signature verification failed: the signature provided isn’t an Ed25519 signature
 
-The signature specified in a [`signature`](signatureHeader) header is not a
-base64-encoded 512 bit byte sequence, and can therefore not be verified as an
+The signature specified in a [`signature`](signatureHeader) header isn’t a
+base64-encoded 512 bit Byte Sequence, and can therefore not be verified as an
 Ed25519 signature.

package/build/src/third_party/issue-descriptions/sriValidationFailedSignatureExpired.md

@@ -1,6 +1,6 @@
-# Signature verification failed: the signature is expired.
+# Signature verification failed: the signature is expired
 
 The [`expires` parameter](signatureParameters) specified in a
 [`signature-input`](signatureInputHeader) header is a UNIX timestamp
 representing a time in the past. The signature has therefore expired, and
-verification is not possible.
+verification isn’t possible.

package/build/src/third_party/issue-descriptions/sriValidationFailedSignatureMismatch.md

@@ -1,7 +1,7 @@
-# Signature verification failed.
+# Signature verification failed
 
 The public key specified in the [`signature-input`](signatureInputHeader)
-header's [`keyid` parameter](signatureParameters) does not match the signature
+header’s [`keyid` parameter](signatureParameters) doesn’t match the signature
 specified in the [`signature`](signatureHeader) header. Verification failed.
 
 The following is the signature base over which the verification attempt was made:

package/build/src/third_party/issue-descriptions/stylesheetLateImport.md

@@ -1,4 +1,4 @@
 # Define @import rules at the top of the stylesheet
 
-An @import rule was ignored because it wasn't defined at the top of the stylesheet. Such rules must appear at the top,
+An @import rule was ignored because it wasn’t defined at the top of the stylesheet. Such rules must appear at the top,
 before any style declaration and any other at-rule with the exception of @charset and @layer.

package/build/src/third_party/issue-descriptions/summaryElementAccessibilityInteractiveContentSummaryDescendant.md

@@ -1,3 +1,3 @@
 # Interactive element inside of a <summary> element
 
-An interactive element was found within a `<summary>` element. These elements will not consistently be accessible to people navigating by keyboard or using assistive technology.
+An interactive element was found within a `<summary>` element. These elements won’t consistently be accessible to people navigating by keyboard or using assistive technology.

package/build/src/third_party/issue-descriptions/unencodedDigestIncorrectDigestLength.md

@@ -1,7 +1,7 @@
-# An `unencoded-digest` header contains a digest with an incorrect length.
+# An `unencoded-digest` header contains a digest with an incorrect length
 
 [`unencoded-digest`](unencodedDigestHeader) headers contain SHA2 digests of a
-response's body. The digest delivered with this response is not the correct
+response’s body. The digest delivered with this response isn’t the correct
 length for the algorithm specified. SHA-256 digests should be 256 bits long,
 SHA-512 digests 512 bits long. For example, if the body was "Hello, world.", the
 following might be an appropriate header:

package/build/src/third_party/issue-descriptions/unencodedDigestIncorrectDigestType.md

@@ -1,10 +1,10 @@
-# An `unencoded-digest` header contains a digest with an invalid type.
+# An `unencoded-digest` header contains a digest with an invalid type
 
 [`unencoded-digest`](unencodedDigestHeader) headers must be formatted as a
-[Dictionary](sfDictionary), wherein each member's label specifies the hashing
+[Dictionary](sfDictionary), wherein each member’s label specifies the hashing
 algorithm, and the value is a [Byte Sequence](sfByteSequence) containing the
 digest. The digest delivered with this response did not deliver the digest as a
-byte sequence.
+Byte Sequence.
 
 For example, if the body was "Hello, world.":
 

package/build/src/third_party/issue-descriptions/unencodedDigestMalformedDictionary.md

@@ -1,7 +1,7 @@
-# An `unencoded-digest` header cannot be parsed.
+# An `unencoded-digest` header can’t be parsed
 
 [`unencoded-digest`](unencodedDigestHeader) headers must be formatted as a
-[Dictionary](sfDictionary), wherein each member's label specifies the hashing
+[Dictionary](sfDictionary), wherein each member’s label specifies the hashing
 algorithm, and the value is a [Byte Sequence](sfByteSequence) containing the
 digest. The digest delivered with this response did not format the response
 correctly.

package/build/src/third_party/issue-descriptions/unencodedDigestUnknownAlgorithm.md

@@ -1,4 +1,4 @@
-# An `unencoded-digest` header contains a digest with an invalid algorithm.
+# An `unencoded-digest` header contains a digest with an invalid algorithm
 
 [`unencoded-digest`](unencodedDigestHeader) headers support only two hashing
 algorithms, SHA-256, and SHA-512. The digests delivered with this response