feat(fr.md): Update FR docs with tooling usages

Author: Attamusc

docs/first-responder.md

@@ -1,7 +1,5 @@
 # First Responder
 
-_The first responder may also be pinged through PagerDuty if a high severity issue related to an AOR the team owns arises. Very few areas we own have SLOs that trigger an alert, so these will mostly likely be manual triggers from someone._
-
 First Responders are expected to be available during their own working hours, for one work week (no weekends).
 
 ## Why have a First Responder?
@@ -10,6 +8,7 @@ First Responders are expected to be available during their own working hours, fo
 - Reduce context shifting among non-responders.
 - Ensure our stakeholders and partners have an engineer available to engage with them.
 - Be a learning and growth opportunity for team members, to gain exposure to more of our areas of responsibility.
+- The first responder may also be pinged through PagerDuty if a high severity issue related to an AOR the team owns arises. **Note: Very few areas we own have SLOs that trigger an alert, so these will mostly likely be manual triggers from someone.**
 
 ## How to First Responder
 
@@ -26,9 +25,7 @@ First Responders are expected to be available during their own working hours, fo
 - [ ] Be the first point of contact for [Pull Request](https://github.com/search?q=is%3Aopen+is%3Apr+team-review-requested%3Agithub%2Fmonolith-platform-reviewers+draft%3Afalse+-label%3Atriage&type=pullrequests) reviews.
 - [ ] Review `#monolith-platform` for notifications throughout each day.
     - [ ] Triage new issues that pop up in the [first responder board](https://github.com/orgs/github/projects/7910). **Note, this board is populated by the github/first-responder tooling.**
-    - [ ] Team pings can be reviewed in `monolith-platform-ops` using the `github/first-responder` tooling chatops
-        - [ ] `.fr sup` to see a list of notifications
-        - [ ] `.fr hide <url>` to hide a notification that's been acted on
+    - [ ] Team pings can be reviewed in `monolith-platform-ops` using the `github/first-responder` tooling chatops (see `First Responder tooling` below)
     - [ ] For questions, try to follow this workflow:
         - [ ] If you know the answer, reply to the person asking the question.
         - [ ] If you don't know the answer immediately, let the requester know that you're researching their problem, and will get back to them. Look through the Hub, documentation, relevant code, and/or ask in the team channel to try to find an answer. **Don't get too hung up on if you can't find an answer. This should be a good effort investigation to make progress, not to solve the ask wholesale.**
@@ -41,7 +38,18 @@ First Responders are expected to be available during their own working hours, fo
 - [ ] Check the [first responder board](https://github.com/orgs/github/projects/7910) for small, refined tasks to take on.
 - [ ] If things are quiet, contribute to normal Epic work. If unsure what to focus on, reach out to @attamusc.
 
+### First Responder tooling
+
+#### chatops
+
+| Action | Chatops command |
+| -------|-- |
+| View active notifications | `.fr new` or `.fr sup` |
+| Hide a notification from .fr new | `.fr hide <url>` |
+| Add an issue to .fr new | `.fr unhide <url>` |
+
 ## End of Shift Report
 
 Add a comment to the [first responder roll-off discussion](https://github.com/github/monolith-platform/discussions/16), describing how the week went and highlight what you think is relevant for the next First Responder.
 
+