We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This issue was originally filed in filecoin-docs by @kt-wawro as filecoin-project/filecoin-docs#1950. Redirecting here, as this is a spec repo issue:
On the filecoin docs on the storage miner sub-pages and blockchain subpages none of the links take you anywhere.
Sealing a sector does not link anywhere but the URL changes to (https://spec.filecoin.io/systems/filecoin_mining/storage_mining/#section-_index.Sealing-a-Sector)
Sector Storage and Window PoSt scheduler have broken links
Sector Sealing has a broken link to the Lotus-specific function at the end of the sector sealing section in sector quality.
I spot-checked links on the following pages and they all seem to be working:
The text was updated successfully, but these errors were encountered:
and we go full circle, as I think I've fixed these already, but not being able to get the PR out: #1314 is what triggered the whole CI discussion...
Sorry, something went wrong.
No branches or pull requests
This issue was originally filed in filecoin-docs by @kt-wawro as filecoin-project/filecoin-docs#1950. Redirecting here, as this is a spec repo issue:
Original issue description
On the filecoin docs on the storage miner sub-pages and blockchain subpages none of the links take you anywhere.
Sealing a sector does not link anywhere but the URL changes to (https://spec.filecoin.io/systems/filecoin_mining/storage_mining/#section-_index.Sealing-a-Sector)
Sector Storage and Window PoSt scheduler have broken links
Sector Sealing has a broken link to the Lotus-specific function at the end of the sector sealing section in sector quality.
I spot-checked links on the following pages and they all seem to be working:
The text was updated successfully, but these errors were encountered: