Merge pull request #6159 from ministryofjustice/runbooks-update

update review dates and modify some punctuation

runbooks/source/how-we-work.html.md.erb

@@ -1,7 +1,7 @@
 ---
 title: How We Work
 weight: 10
-last_reviewed_on: 2024-06-11
+last_reviewed_on: 2024-09-11
 review_in: 3 months
 ---
 
@@ -19,11 +19,11 @@ If you need help at any point, don't hesitate to ask the team. Among other thing
 
 ## Sprints and ceremonies
 
-We work in two-week sprints - these are usually product led.
+We work in two-week sprints - these are usually product-led.
 Our team ceremonies include: daily stand up at 10:30am on Google Meet, planning every forth-night on Wednesday and our sprint demo followed by retro on Thursday.
 
 ### Firebreak
-For 1 sprint every 2 months, we have a Firebreak sprint. Firebreaks are team led and provides team members the opportunity to work on tickets that are of interest to them and also of value to the organisation such as:
+For 1 sprint every 2 months, we have a Firebreak sprint. Firebreaks are team-led and provide team members the opportunity to work on tickets that are of interest to them and also of value to the organisation such as:
 
 1. Address tech debt
 2. Prototyping innovative new features

runbooks/source/kibana-podsecurity-violations-alert.html.md.erb

@@ -1,9 +1,8 @@
 ---
 title: Kibana PodSecurity Violations Alert
 weight: 191
-last_reviewed_on: 2024-06-11
+last_reviewed_on: 2024-09-11
 review_in: 3 months
-reviewer: Jack Stockley
 ---
 
 # Kibana PodSecurity Violations Alert
@@ -25,7 +24,7 @@ To diagnose which namespace(s) are violating and to see the reason in the logs,
 
 Or follow [this link](https://kibana.cloud-platform.service.justice.gov.uk/_plugin/kibana/app/discover#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-5h,to:now))&_a=(columns:!(_source),filters:!(),index:'167701b0-f8c0-11ec-b95c-1d65c3682287',interval:auto,query:(language:kuery,query:'%22violates%20PodSecurity%22%20AND%20NOT%20%22smoketest-restricted%22%20AND%20NOT%20%22smoketest-privileged%22'),sort:!())) to get the same search.
 
-This will show any logs of PSA violations (excluding smoketests). If no logs appear then increase the time frame to match when the alert was triggered, you can check this on the monitor under the `Alerts` heading.
+This will show any logs of PSA violations (excluding smoketests). If no logs appear, then increase the time frame to match when the alert was triggered. You can check this on the monitor under the `Alerts` heading.
 
 In the logs, it will provide information such as the offending namespace and the reason it has been triggered.
 
@@ -37,4 +36,4 @@ To fix a PSA violation and stop the monitor from triggering, gather the namespac
 
 Kibana will put a message into the `#low-priority-alarms` slack channel whenever the [PodSecurity Violations monitor](https://kibana.cloud-platform.service.justice.gov.uk/_plugin/kibana/app/opendistro-alerting#/monitors/jR-J3YsBP8PE0GofcRIF) first goes into the `Triggered` status.
 
-The monitor is throttled to only send 1 message every 24 hours per trigger. This means if a namespace is already triggering the monitor then when another violation occurs then it will not send another message. The best way to check what is triggering the monitor is to use the steps mentioned above under [Checking logs for PSA violation in Kibana](#checking-logs-for-psa-violations-in-kibana).
+The monitor is throttled to only send 1 message every 24 hours per trigger. This means if a namespace is already triggering the monitor then when another violation occurs, then it will not send another message. The best way to check what is triggering the monitor is to use the steps mentioned above under [Checking logs for PSA violation in Kibana](#checking-logs-for-psa-violations-in-kibana).