Commit f66380b9 authored by Daniel Thompson-Yvetot's avatar Daniel Thompson-Yvetot
Browse files

Merge branch 'typos' into 'main'

fix some typos

See merge request cyber/stan4cr2/en-304-617!19
parents a4728da3 104f380d
Loading
Loading
Loading
Loading
+4 −4
Original line number Diff line number Diff line
@@ -189,7 +189,7 @@ In a PWA or Progressive Web App, an application can be “installed” to the us

## 2.1 Normative references

_**In Harmonised Standards these references shall be specific** (identified by date of publication and/or edition number or version number) **publicly available and in English, except in exceptional circumstances making sure that impacts have been evaluated and explanations have been given on how any negative implications should be avoided** . See clauses 2.10.1 and 8.4 of the [EDRs](EDRs) and the communiqué on "[References in ETSI Deliverables](https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/News_from_editHelp/References_in_ETSI_deliverables.pdf)"._
_**In Harmonised Standards these references shall be specific** (identified by date of publication and/or edition number or version number) **publicly available and in English, except in exceptional circumstances making sure that impacts have been evaluated and explanations have been given on how any negative implications should be avoided** . See clauses 2.10.1 and 8.4 of the [EDRs](EDRs) and the communiqué on "[References in ETSI Deliverables](https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/News_from_editHelp/References_in_ETSI_deliverables.pdf)"._

_Guidance for selecting normative references in harmonised standards is given in clause 2.8.3 of the Vademecum on European standardisation. Please **systematically consult with your Technical Officer** for the latest guidance on normative references other than to ENs, ISO/IEC standards, notably to prevent the risk of non-acceptance._

@@ -261,7 +261,7 @@ Custom Protocol: Non-standard or application-specific communication protocols th

Accessing Webcontent: The complete process by which browsers retrieve, process, and present web resources to end users, encompassing network communication, content parsing, rendering, and user interface presentation.

Secondary fFnctionalities: Supplementary browser capabilities that support the primary browsing function, including but not limited to managing software updates, executing installation scripts, validating security certificates, and maintaining browser performance and security.
Secondary Functionalities: Supplementary browser capabilities that support the primary browsing function, including but not limited to managing software updates, executing installation scripts, validating security certificates, and maintaining browser performance and security.

Likelihood: The probability or frequency of a threat event occurring within the browser ecosystem, quantified through analysis of threat intelligence, historical incident data, and environmental factors affecting browser security.

@@ -317,7 +317,7 @@ The following types of products have reduced or varied requirements under the Cy

## 4.4 Use Cases

#TODO: Maybe we have been looking at things too closely in line with the notably artifical demarcation between "Standalone and embedded" browsers. Perhaps these two are really just use cases of browsers, and a third "high-level" use case is the PWA.
#TODO: Maybe we have been looking at things too closely in line with the notably artificial demarcation between "Standalone and embedded" browsers. Perhaps these two are really just use cases of browsers, and a third "high-level" use case is the PWA.

## 4.4.1 Purpose and Rationale