Update index.md doc links, Slack channels, etc...

content/departments/engineering/teams/release/index.md

@@ -20,18 +20,17 @@ For more detailed information on the Release team members, check out our [README
   - [Kubernetes - Helm](https://github.com/sourcegraph/deploy-sourcegraph-helm)
   - [Kubernetes - kustomize](https://github.com/sourcegraph/deploy-sourcegraph-k8s)
   - [docker](https://github.com/sourcegraph/deploy-sourcegraph-docker)
-- [Customer deployments and docs](https://docs.sourcegraph.com/admin/install)
-- [Org-wide areas of ownership](../../dev/process/engineering_ownership.md#delivery-and-delivery-tiger-team)
-- [Sourcegraph releases](../../dev/process/releases/index.md) releases are owned by the Release Team.
+- [Customer deployments and docs](https://sourcegraph.com/docs/admin/deploy)
+- [Sourcegraph releases](../../dev/process/releases/index.md) are owned by the Release Team.
 
 ## Contact
 
-- #discuss-release-ship, or `@release-team` in Slack. Please follow our [support guidelines](#support-request-guidelines) below.
+- #discuss-releases, or `@release-team` in Slack. Please follow our [support guidelines](#support-request-guidelines) below.
 - [team/release](https://github.com/sourcegraph/sourcegraph/labels/team%2Frelease-ship) label and [@sourcegraph/release](https://github.com/orgs/sourcegraph/teams/release) team on GitHub.
 
 ## Support
 
-If in doubt about the process, please ask in #discuss-release-ship. Teammates shold consult our [support-rotation](./processes.md#support-rotation) guide to handle inquiries.
+If in doubt about the process, please ask in #discuss-releases. Teammates should consult our [support-rotation](./processes.md#support-rotation) guide to handle inquiries.
 
 ### Requesting our support
 
@@ -50,11 +49,11 @@ Support requests related to our [areas of ownership](./#responsibilities) should
    - A more detailed explanation of the background, the context and the challenge that needs solving
    - Any guidance related to the impact this is having
    - Any extra information that could help us solve or prioritize this
-2. Ensure lable `team/release` is added to the issue
+2. Ensure label `team/release` is added to the issue
 3. Ensure that the issue is added to the "[Release](https://github.com/orgs/sourcegraph/projects/362)" board in GitHub
 4. Anything without a status is checked and triaged weekly - so this is enough for feature requests or less urgent issues
 5. If you think this needs eyes 👀 sooner
-   - Within a few hours ➡️ message in #discuss-release-ship
+   - Within a few hours ➡️ message in #discuss-releases
    - ASAP ➡️ message in #team-releases and CC `@release-team`
 
 <!-- ## Growth plan