summaryrefslogtreecommitdiff
path: root/gemfeed/2021-10-22-defensive-devops.gmi
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2022-01-03 12:38:52 +0000
committerPaul Buetow <paul@buetow.org>2022-01-03 12:38:52 +0000
commitda0fbc0c00190e431b66d46c589b65aa13a406f7 (patch)
tree6ef0104d9d392d255504c5c42a584e7d33f1f93f /gemfeed/2021-10-22-defensive-devops.gmi
parentd409fec1404a4ac5718cefd658b682934f11ee45 (diff)
change email me your .... phrase sentence at the end of each post
Diffstat (limited to 'gemfeed/2021-10-22-defensive-devops.gmi')
-rw-r--r--gemfeed/2021-10-22-defensive-devops.gmi2
1 files changed, 1 insertions, 1 deletions
diff --git a/gemfeed/2021-10-22-defensive-devops.gmi b/gemfeed/2021-10-22-defensive-devops.gmi
index fab1509f..771c1560 100644
--- a/gemfeed/2021-10-22-defensive-devops.gmi
+++ b/gemfeed/2021-10-22-defensive-devops.gmi
@@ -99,6 +99,6 @@ For every major incident, you need to follow up with an incident retrospective.
This usually means creating one or more tickets, which will be dealt with soon. Once the permanent fix is deployed, you can remove your ad-hoc automation and monitoring around it and focus on your regular work again.
-E-Mail me your thoughts at snonux@snonux.de!
+E-Mail me your comments to snonux@snonux.de!
=> ../ Go back to the main site