Skip to content

Commit 02aba14

Browse files
author
Michael Colburn
committed
formatting
1 parent eabec35 commit 02aba14

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

development-guidelines/incident_response.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ How you respond during an incident is a direct reflection of your efforts to pre
2424
## Process
2525

2626
- **Conduct periodic training and incident response exercises**. Regularly organize training sessions and incident response exercises. Such measures ensure that employees remain updated and can help highlight any flaws in the current incident response protocol.
27-
- **Remember to consider off-chain components when planning**. While much of this document is concerned with on-chain code, compromised frontends or social media accounts are also common sources of incidents.
27+
- **Remember to consider off-chain components when planning**. While much of this document is concerned with on-chain code, compromised frontends or social media accounts are also common sources of incidents.
2828
- **Identify incident owners, with at least**:
2929
- **A technical lead**. Responsible for gathering and centralizing technical data.
3030
- **A communication lead**. Tasked with internal and external communication.

0 commit comments

Comments
 (0)