nft storage removal from Sugar and some other upload locations

src/pages/candy-machine/guides/create-an-nft-collection-on-solana-with-candy-machine.md

@@ -259,7 +259,6 @@ The config file will look like this:
   "ruleSet": null,
   "awsConfig": null,
   "sdriveApiKey": null,
-  "nftStorageAuthToken": null,
   "shdwStorageAccount": null,
   "pinataConfig": null,
   "hiddenSettings": null,

src/pages/candy-machine/insert-items.md

@@ -29,8 +29,8 @@ Additionally, tools like [Sugar](/candy-machine/sugar) make uploading JSON metad
 Umi ships with an `uploader` interface that can be used to upload JSON data to the storage provider of your choice. For instance, this is how you'd select the NFT.Storage implementation of the uploader interface.
 
 ```ts
-import { nftStorage } from '@metaplex-foundation/umi-uploader-nft-storage'
-umi.use(nftStorageUploader({ token: 'YOUR_API_TOKEN' }))
+import {irysUploader } from '@metaplex-foundation/umi-uploader-irys'
+umi.use(irysUploader())
 ```
 
 You may then use the `upload` and `uploadJson` methods of the `uploader` interface to upload your assets and their JSON metadata.

src/pages/candy-machine/sugar/configuration.md

@@ -30,7 +30,6 @@ A basic configuration file is shown below:
   "hiddenSettings": null,
   "uploadMethod": "bundlr",
   "awsConfig": null,
-  "nftStorageAuthToken": null,
   "shdwStorageAccount": null,
   "pinataConfig": null,
   "sdriveApiKey": null,
@@ -142,7 +141,6 @@ The table below provides an overview of the settings available:
 | uploadMethod |   |  | Configure the storage to upload images and metadata |  
 |  |   | "bundlr" |  Uploads to Arweave using [Bundlr](https://bundlr.network) and payments are made in SOL (works on both mainnet and devnet; files are only stored for 7 days on devnet)
 |  |   | "aws" | Uploads to Amazon Web Services (AWS) |
-|  |   | "nftStorage" | Uploads to [NFT.Storage](https://nft.storage) (works on all networks) |
 |  |   | "shdw" | Uploads to the GenesysGo [Shadow Drive](https://docs.shadow.cloud) (works on mainnet only)
 |  |   | "pinata" | Uploads to [Pinata](https://www.pinata.cloud) (works on all networks; free and tiered subscriptions) |
 |  |   | "sdrive" | Uploads to Shador Drive using [SDrive Cloud Storage](https://sdrive.app) |
@@ -150,7 +148,6 @@ The table below provides an overview of the settings available:
 | | bucket | String | AWS bucket name
 | | profile | String | AWS profile to use from the credentials file name |
 | | directory | String | The directory within the bucket to upload the items to. An empty string means uploading files to the bucket root directory. |
-| nftStorageAuthToken | | String | NFT.Storage API Key *(required when "nftStorage" is used)* |
 | pinataConfig | | | *(required when "pinata" is used)* |
 | | JWT | String | JWT authentication token |
 | | apiGateway | String | URL to connect to Pinata API |
@@ -185,11 +182,6 @@ It is also important to set up the ACL permission of the bucket correctly to ena
 
 The `profile` value allows you to specify which profile to read from your credentials file. The `directory` value is the name of the directory in the bucket where the files will be uploaded, allowing you to have multiple candy machine or collections in a single bucket separated by different directories. Leaving this as an empty string will upload the files to the root of the bucket. The (optional) `domain` allows you to specify a custom domain to serve the data from AWS — e.g., using the domain as `https://mydomain.com` will create links to files in the format `https://mydomain.com/0.json`. If you do not specify a domain, the default AWS S3 domain will be used (`https://<BUCKET_NAME>.s3.amazonaws.com`).
 
-{% /totem-accordion %}
-{% totem-accordion title="NFT.Storage" %}
-
-NFT.Storage is a popular service that uploads data on the public IPFS network. You will need to register an account to obtain an API key (token), which need to be specified by `"nftStorageAuthToken"` in the configuration file.
-
 {% /totem-accordion %}
 {% totem-accordion title="Pinata" %}
 

src/pages/core/create-asset.md

@@ -15,7 +15,7 @@ Let's dig into these steps in more detail, whilst providing concrete code exampl
 
 ## Uploading off-chain data
 
-You may use any storage service (Arweave, IPFS, AWS etc...) to upload your off-chain data or simply store it on your own server. To make some of these easier for the user `Umi` has some dedicated plugins including the likes of `Irys (uploads to Arweave)` and `nftStorage (uploads to IPFS)`. Once a plugin is selected this grants the user a unified interface for you to upload your data.
+You may use any storage service (Arweave, IPFS, AWS etc...) to upload your off-chain data or simply store it on your own server. To make some of these easier for the user `Umi` has some dedicated plugins including the likes of `Irys (uploads to Arweave)`. Once a plugin is selected this grants the user a unified interface for you to upload your data.
 
 {% dialect-switcher title="Upload assets and JSON data" %}
 {% dialect title="JavaScript" id="js" %}

src/pages/core/guides/javascript/how-to-create-a-core-collection-with-javascript.md

@@ -180,7 +180,7 @@ const umi = createUmi('https://api.devnet.solana.com')
 
 ## Creating the Metadata for the Collection
 
-To display a recognisable image for your Collection in the Wallets or on the Explorer, we need to create the URI where we can store the Metadata!
+To display a recognizable image for your Collection in the Wallets or on the Explorer, we need to create the URI where we can store the Metadata!
 
 ### Uploading the Image