Update content/docs/administration-guidelines.md

content/docs/administration-guidelines.md

@@ -28,7 +28,7 @@ Please prioritise contacting a community team member over non community team mem
 ## General Administration Guidelines
 - The primary job of administrators is to maintain and develop programming.dev, both as a site and community. They should *strictly* enforce the rules and guidelines as laid out on https://legal.programming.dev/. This means that administrators should do their best to coordinate a similar interpretation of the rules and guidelines, and avoid adding their own flavour and personal rules that are not discussed and agreed upon by the rest of the admin team.  
  Note that we acknowledge that there may be grey areas, loopholes or contexts that are not directly covered by the guidelines, if an administrator encounters a case without any pre-established guidelines, they should consult the admin team before taking action. The written rules and guidelines does not supersede the collective opinion and conclusion the admin team may reach on a specific case. The guidelines should be updated to cover the gap for repeated cases.
-- Administrators are expected to follow the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md) to the highest standard, this applies to both their admin account and any other accounts they have that links them to programming.dev.
+- Administrators are expected to follow the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct) to the highest standard, this applies to both their admin account and any other accounts they have that links them to programming.dev.
   Acts that qualify to linking their alt-accounts with their admin account are as follows:
   - Accounts with an identical name or references to their admin account, be it a local account or an account linked to programming.dev via the ActivityPub protocol.
   - They have revealed that they are an admin on programming.dev on their alt-account.
@@ -37,18 +37,18 @@ Please prioritise contacting a community team member over non community team mem
   - They have via any other way interleaved their alt-accounts such that someone interacting with their alt-account knows they are interacting with a programming.dev admin.
 - It is recommended that administrators avoid getting into heated arguments with users. Administrators should as soon as they realise an argument is getting too heated or off-topic try to either de-escalate or disengage from the argument.
 - If an administrator wishes to engage in controversial topics, it is recommended that they use an alternate account not linked to their admin account. While this is only a recommendation, it is a highly recommended one as the site has been drawn into needless admin drama with other instances as a result of this guideline not being followed in the past.
-- Administrators are not allowed to moderate content they are personally entangled with. If a user posts a severe breach of the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md) that affects an administrator, the administrator should report the content and leave it to the rest of the admin team to handle. The administrator may not comment on the case unless questioned by the admin team and may under no circumstances suggest what action to take. The administrator is still allowed to temporarily remove the content if deemed necessary, such as in the instance of being doxxed, the administrator must however also immediately notify the admin team that they have taken such action. Breaking this *rule* is considered a severe breach of trust and power. Exceptions are made for CSAM, phishing attempts, or established spam/scam similar to the [Nicole spam](https://programming.dev/c/nicole@feddit.org).
+- Administrators are not allowed to moderate content they are personally entangled with. If a user posts a severe breach of the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct) that affects an administrator, the administrator should report the content and leave it to the rest of the admin team to handle. The administrator may not comment on the case unless questioned by the admin team and may under no circumstances suggest what action to take. The administrator is still allowed to temporarily remove the content if deemed necessary, such as in the instance of being doxxed, the administrator must however also immediately notify the admin team that they have taken such action. Breaking this *rule* is considered a severe breach of trust and power. Exceptions are made for CSAM, phishing attempts, or established spam/scam similar to the [Nicole spam](https://programming.dev/c/nicole@feddit.org).
 
 
 
 ## When to Perform Admin Actions
 - As a general rule, administrators should leave moderation to moderators. If an administrator steps in on behalf of a moderator, they should follow the guidelines as laid out in [Acting on Behalf of Moderators](#acting-on-behalf-of-moderators).
-- If user content is breaking the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md) and the severity is high enough to warrant admin action rather than waiting for mod action, the administrator must follow the protocol [Enforcing Programming.dev's Code of Conduct](#enforcing-programmingdevs-code-of-conduct) when deciding on what action to take. The boundary between when the severity is high enough for an administrator to step in and take action is purposefully left diffuse, but a guideline is that it at a minimum shouldn't be left to interpretation if the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md) has been breached or not.
-- An administrator should never take administrative action on content that isn't strictly against our [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md). If an administrator believes they've found content that requires administrative action, but isn't covered by the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md), they should always consult with rest of the admin team before taking action.
+- If user content is breaking the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct) and the severity is high enough to warrant admin action rather than waiting for mod action, the administrator must follow the protocol [Enforcing Programming.dev's Code of Conduct](#enforcing-programmingdevs-code-of-conduct) when deciding on what action to take. The boundary between when the severity is high enough for an administrator to step in and take action is purposefully left diffuse, but a guideline is that it at a minimum shouldn't be left to interpretation if the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct) has been breached or not.
+- An administrator should never take administrative action on content that isn't strictly against our [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct). If an administrator believes they've found content that requires administrative action, but isn't covered by the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct), they should always consult with rest of the admin team before taking action.
 - If an administrator is not 100% sure if they should take action, they should consult with the rest of the admin team before taking action.
-- Administrators should not moderate what federated users post on other federated instances. It sets a bad precedent and gives the admin team a workload it likely can't handle. We assume that federated instances comply with our [Defederation Policy](https://legal.programming.dev/docs/defederation-policy.md) and that administrators of the other instance will take action if necessary. Exceptions can be made for content of severity 4.
+- Administrators should not moderate what federated users post on other federated instances. It sets a bad precedent and gives the admin team a workload it likely can't handle. We assume that federated instances comply with our [Defederation Policy](https://legal.programming.dev/docs/defederation-policy) and that administrators of the other instance will take action if necessary. Exceptions can be made for content of severity 4.
 - Actions may be taken on our local users regardless of which instance they are interacting with, and on federated users that are interacting with our local users and communities.
-- Admin moderated communities may be treated as site-wide communities, meaning that administrators may choose to apply admin actions instead of mod actions to content posted in those communities. This means that rather than banning someone from e.g. [programming@programming.dev](https://programming.dev/c/programming), they may ban them from the entire site. Such action can only be taken on content that breaks the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md). Breaches on community specific rules follow the guidelines in [Acting on Behalf of Moderators](#acting-on-behalf-of-moderators).
+- Admin moderated communities may be treated as site-wide communities, meaning that administrators may choose to apply admin actions instead of mod actions to content posted in those communities. This means that rather than banning someone from e.g. [programming@programming.dev](https://programming.dev/c/programming), they may ban them from the entire site. Such action can only be taken on content that breaks the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct). Breaches on community specific rules follow the guidelines in [Acting on Behalf of Moderators](#acting-on-behalf-of-moderators).
 
 
 ### Guidelines on Content Severity
@@ -85,7 +85,7 @@ A strike is decremented by 1 after 365 days without any further violations, for
 4\. If the user repeats a violation after a temporary ban, a permanent ban may be issued.
 
 ### Enforcing Programming.dev's Code of Conduct
-If a user is found to be in violation of the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md), the following steps should be taken:
+If a user is found to be in violation of the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct), the following steps should be taken:
 
 - Check if the user has previously been logged by another admin in the admin log, as of writing that would be #pd-warnings channel on discord.
 - Enforce the 3-4 strike system based on previous history.