docs: missed some spots

status/raw/status-app-protocols.md

@@ -14,7 +14,7 @@
 ## Abstract
 
 This specification describes the Status Application protocol stack.
 It focuses on elements and features in the protocol stack for all application-level functions:
 
 - functional scope (also _broadcast audience_)
 - content topic
@@ -23,7 +23,7 @@
 - encryption layer
 - transport layer (Waku)
 
 It also introduces strategies to restrict resource usage, distribute large messages, etc.
 Application-level functions are out of scope and specified separately. See:
 
 - [55/STATUS-1TO1-CHAT](../55/1to1-chat.md)
@@ -53,31 +53,31 @@
 - Status 1:1 Chat, as specified in [55/STATUS-1TO1-CHAT](../55/1to1-chat.md)
 - Status Private Group Chat, as specified in a subsection of [55/STATUS-1TO1-CHAT](../55/1to1-chat.md#negotiation-of-a-11-chat-amongst-multiple-participants-group-chat)
 
 <!-- TODO: list functions not related to main app features, such as user sync, backup, push notifications, etc. -->
 
 Each application-level function, regardless which feature set it supports, has the following properties:
 
 1. Functional scope
-2. Content topic
-3. Ephemerality
+1. Content topic
+1. Ephemerality
 
 ### Functional Scope
 
 Each Status app-level message MUST define a functional scope.
 The functional scope MUST define the _minimum_ scope of the audience that should _participate_ in the app function the message is related to.
 In other words, it determines the minimum subset of Status app participants
 that should have access to messages related to that function.
 
 Note that the functional scope is distinct from the number of participants that is _addressed_ by a specific message.
 For example, a participant will address a 1:1 chat to only one other participant.
 However, since all users of the Status app MUST be able to participate in 1:1 chats,
 the functional scope of messages enabling 1:1 chats MUST be a global scope.
 Similarly, since private group chats can be set up between any subset of Status app users,
 the functional scope for messages related to private group chats MUST be global.
 As a counter-example, messages that originate within a community (and are _addressed_ to members of that community)
 are only of interest to participants that are also members of that community.
 Such messages MUST have a community-wide functional scope.
 A third group of messages are addressed only to the participant that generated those messages itself.
 These _self-addressed_ messages MUST have a local functional scope.
 
 If we further make a distinction between "control" and "content" messages,
@@ -87,7 +87,7 @@
 
 #### Global scope
 
 1. _Global control_: messages enabling the basic functioning of the app to control features that all app users should be able to participate in. Examples include Contact Requests, Community Invites, global Status Updates, Group Chat Invites, etc.
 2. _Global content_: messages carrying user-generated content for global functions. Examples include 1:1 chat messages, images shared over private group chats, etc.
 
 #### Community scope
@@ -140,7 +140,7 @@
 The end-to-end reliability layer contains the functions related to one of the two end-to-end reliability schemes defined for Status app messages:
 
 1. Minimum Viable protocol for Data Synchronisation, or MVDS (see [STATUS-MVDS-USAGE](./status-mvds.md))
-2. Scalable distributed log reliability (spec and a punchier name TBD, see the [original forum post announcement](https://forum.vac.dev/t/end-to-end-reliability-for-scalable-distributed-logs/293/16))
+1. Scalable distributed log reliability (spec and a punchier name TBD, see the [original forum post announcement](https://forum.vac.dev/t/end-to-end-reliability-for-scalable-distributed-logs/293/16))
 
 Ephemeral messages SHOULD omit this layer.
 Non-ephemeral 1:1 chat messages SHOULD make use of MVDS to achieve reliable data synchronisation between the two parties involved in the communication.