From a7192d8f7a2deb6feb83a2b50eabcf316867caf4 Mon Sep 17 00:00:00 2001 From: Alan Shaw Date: Wed, 13 Dec 2023 14:31:51 +0000 Subject: [PATCH] chore: appease linter --- src/pages/docs/how-to/remove.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/pages/docs/how-to/remove.mdx b/src/pages/docs/how-to/remove.mdx index 908a537..1a0faa3 100644 --- a/src/pages/docs/how-to/remove.mdx +++ b/src/pages/docs/how-to/remove.mdx @@ -48,11 +48,11 @@ If you have managed your shard CIDs and upload CIDs separately (e.g., used `clie To remove shard CIDs and upload CIDs separately, you'll generally do this by: 1. Determine shards to remove (skip this step if you already know!): - - Client: `client.capability.upload.list(contentCID)` - - CLI: `w3 can upload ls --shards` + - Client: `client.capability.upload.list(contentCID)` + - CLI: `w3 can upload ls --shards` 1. Remove the upload: - - Client: `client.capability.upload.remove(contentCID)` - - CLI: `w3 can upload rm ` + - Client: `client.capability.upload.remove(contentCID)` + - CLI: `w3 can upload rm ` 1. Remove each of the shards (ensure first that no other content is using that shard!): - - Client: `client.capability.store.remove(shardCID)` - - CLI: `w3 can store rm ` + - Client: `client.capability.store.remove(shardCID)` + - CLI: `w3 can store rm `