fix links

Author: paigecalvert

docs/vendor/ci-workflows.mdx

@@ -299,4 +299,4 @@ Consider the following requirements and recommendations:
 
 Finally, add a job to archive the temporary channel and customer that you created. This ensures that these artifacts are removed from your Replicated team and that they do not have to be manually archived after the release is promoted.
 
-See the [channel delete](/reference/replicated-cli-channel-delete) Replicated CLI command and the [customer/\{customer_id\}/archive](https://replicated-vendor-api.readme.io/reference/archivecustomer) endpoint in the Vendor API v3 documentation. Or, for GitHub Actions workflows, see the [archive-channel](https://github.com/replicatedhq/replicated-actions/tree/main/archive-channel) and [archive-customer](https://github.com/replicatedhq/replicated-actions/tree/main/archive-customer) actions.
+See the [channel rm](/reference/replicated-cli-channel-rm) Replicated CLI command and the [customer/\{customer_id\}/archive](https://replicated-vendor-api.readme.io/reference/archivecustomer) endpoint in the Vendor API v3 documentation. Or, for GitHub Actions workflows, see the [archive-channel](https://github.com/replicatedhq/replicated-actions/tree/main/archive-channel) and [archive-customer](https://github.com/replicatedhq/replicated-actions/tree/main/archive-customer) actions.

docs/vendor/releases-creating-channels.md

@@ -67,4 +67,4 @@ To archive a channel with the Vendor Portal or the Replicated CLI:
      ```
      Replace `CHANNEL_ID` with the channel ID that you retrieved in the previous step.
 
-     For more information, see [channel delete](/reference/replicated-cli-channel-delete) in the Replicated CLI documentation.
+     For more information, see [channel rm](/reference/replicated-cli-channel-rm) in the Replicated CLI documentation.