fix: update oudated discord channel name (#33)

### Explanation

going through training, found that the channel name is outdated from the current setup of the discord server

### Issue

_No response_

### Attestations

- [x] I have read and agree to the [Code of Conduct](https://docs.nhcarrigan.com/community/coc/)
- [x] I have read and agree to the [Community Guidelines](https://docs.nhcarrigan.com/community/guide/).
- [x] My contribution complies with the [Contributor Covenant](https://docs.nhcarrigan.com/dev/covenant/).

### Dependencies

- [ ] I have pinned the dependencies to a specific patch version.

### Style

- [ ] I have run the linter and resolved any errors.
- [x] My pull request uses an appropriate title, matching the conventional commit standards.
- [x] My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request.

### Tests

- [ ] My contribution adds new code, and I have added tests to cover it.
- [ ] My contribution modifies existing code, and I have updated the tests to reflect these changes.
- [ ] All new and existing tests pass locally with my changes.
- [ ] Code coverage remains at or above the configured threshold.

### Documentation

_No response_

### Versioning

Patch - My pull request introduces bug fixes ONLY.

Reviewed-on: #33
Reviewed-by: Naomi Carrigan <accounts@nhcarrigan.com>
Co-authored-by: Ilenia <ilenia@nhcarrigan.com>
Co-committed-by: Ilenia <ilenia@nhcarrigan.com>

src/content/docs/staff/handbook.md

@@ -36,7 +36,7 @@ We recognise and deeply appreciate that our Team members are volunteers dedicati
 
 While we maintain a flexible approach to activity, we kindly request that you inform us of any anticipated absences:
 
-- For absences exceeding one week, please notify the team via the `#staff-chat` channel on Discord.
+- For absences exceeding one week, please notify the team via the `#sentinel-watch` channel on Discord.
 - This communication helps us manage workload distribution and ensures continued smooth operation of our community.
 
 ### 1.3. Extended Inactivity
@@ -187,7 +187,7 @@ Maintain transparency and accountability to the community:
 
 Maintain open lines of communication with your fellow Team members:
 
-- Use designated channels (e.g., `#staff-chat`) to discuss community issues and seek guidance
+- Use designated channels (e.g., `#sentinel-watch`) to discuss community issues and seek guidance
 - Share experiences and seek advice when facing challenging situations
 - Communicate openly about workload, availability, and support needs
 
@@ -223,7 +223,7 @@ All Team members must know when and how to escalate issues appropriately. Escala
 
 **How to Escalate:**
 
-**(a)** **Use Appropriate Channels**: Escalate through designated staff channels (e.g., `#staff-chat` on Discord) or direct contact with relevant coordinators or senior staff.
+**(a)** **Use Appropriate Channels**: Escalate through designated staff channels (e.g., `#sentinel-watch` on Discord) or direct contact with relevant coordinators or senior staff.
 
 **(b)** **Provide Complete Context**: When escalating, include:
 - Clear description of the situation
@@ -281,8 +281,8 @@ For detailed escalation procedures specific to different situations, refer to th
 
 #### 3.1.1. Primary Communication Platforms
 - Our Discord community serves as a primary communication hub for the staff team
-- A private `staff` category is available for internal discussions
-- Discord `#staff-chat` channel for real-time communication and coordination
+- A private `The Inner Circle` category is available for internal discussions
+- Discord `#sentinel-watch` channel for real-time communication and coordination
 
 #### 3.1.2. Use of Staff Communication Channels
 - Utilise staff channels for: