formattign

Signed-off-by: flakey5 <73616808+flakey5@users.noreply.github.com>

docs/sops/incident-flow.md

@@ -12,9 +12,9 @@ Procedure for what to do if there's an incident with the Release Worker.
    incident that we cannot disclose publicly yet, do not includes the details
    of the incident in the status page.
 
-   * Optional, but preferably updates will be echoed on social media.
+   - Optional, but preferably updates will be echoed on social media.
 
-   * Please also monitor any issues in repositories such as
+   - Please also monitor any issues in repositories such as
      this one,
      [nodejs/node](https://github.com/nodejs/node), and
      [nodejs/nodejs.org](https://github.com/nodejs/nodejs.org) for users asking
@@ -23,7 +23,7 @@ Procedure for what to do if there's an incident with the Release Worker.
 3. [Steps for debugging the worker when it's deployed](./debugging.md)
 
 4. If there is an ongoing security incident requiring code changes, a force
-   push to the `main` branch can be performed by a 
+   push to the `main` branch can be performed by a
    [Collaborator](../CONTRIBUTING.md#contributing) if there is reasonable risk
    that opening a PR with the change would allow more bad actors to exploit the
    vulnerability. The code changes must still be approved by another