diff --git a/src/tutorials/0007-verifying-storage-on-filecoin/02.md b/src/tutorials/0007-verifying-storage-on-filecoin/02.md
index b01b41ea4..df7db4b74 100644
--- a/src/tutorials/0007-verifying-storage-on-filecoin/02.md
+++ b/src/tutorials/0007-verifying-storage-on-filecoin/02.md
@@ -15,7 +15,7 @@ Since payload CIDs and piece CIDs are cryptographic hashes of the data itself, t
 
 ## Negotiating a storage deal and transferring data
 
-When a client negotiates a storage deal with a miner, they're hiring them to store a _piece_ of data, which might be a whole or partial file. Miners store these pieces from one or more clients in _sectors_, the fundamental storage unit used by Filecoin. Sectors come in a variety of sizes, and a client can store data up to the largest sector size per deal. (Learn more about [sector sizes and storing large files](https://docs.filecoin.io/how-to/store/prepare-data/#for-files-bigger-than-a-sector).)
+When a client negotiates a storage deal with a miner, they're hiring them to store a _piece_ of data, which might be a whole or partial file. Miners store these pieces from one or more clients in _sectors_, the fundamental storage unit used by Filecoin. Sectors come in a variety of sizes, and a client can store data up to the largest sector size per deal. (Learn more about [sector sizes and storing large files]https://spec.filecoin.io/systems/filecoin_mining/sector/).)
 
 A piece CID is wrapped with other deal parameters to create a Deal Proposal. The _deal CID_ contains information about the data itself, in the form of the piece CID, the identities of the miner and client, and other important transaction details.