@@ -259,7 +259,7 @@ We mark the PagerDuty page as [resolved](#pagerduty-status-definitions) once eve
### **Stage 2: Manage**
After all [Stage 1](#stage-1-engage) tasks have been complete we will manage the incident by making updates to it, creating a tag for it in Zendesk, and responding to any tickets in Zendesk that are related to it.
After all [Stage 1](#stage-1-engage) tasks have been completed we will manage the incident by making updates to it, creating a tag for it in Zendesk, and responding to any tickets in Zendesk that are related to it.
#### Update Incident
@@ -291,7 +291,7 @@ A ready to be published update should look similar to the following.
Twitter has a 280 character limit, but we noticed that some tweets get truncated to 230 characters, such as [this one](https://twitter.com/gitlabstatus/status/1641150257936601088). This can be due to twitter converting any URLs to a 23-character URL via their link shortener service.
X (formerly Twitter) has a 280 character limit, but we noticed that some tweets get truncated to 230 characters, such as [this one](https://twitter.com/gitlabstatus/status/1641150257936601088). This can be due to X converting any URLs to a 23-character URL via their link shortener service.
Make sure to [verify](https://wordcounter.net/character-count) the update length before publishing it, and try to fit the main body of the message (before the final URL to the issue) in 220 characters. This leaves about 10 characters to display the final URL, if it gets truncated.
