Arie comments

[yoav-el-certora]

Naming convention:

• PRs for features that are in design should have the "proposal" label
• PRs for features that haven't landed yet should have the "future" label
• PRs for upcoming releases should have the "release" label
• PRs with new documentation for existing features should have the "existing feature" label

Before requesting review:

• Make sure there is a ticket in the DOC board in Jira
• Make sure CI is passing
  • Spell check failure may require adding backticks around code or updating spelling_wordlist.txt
  • See README.md for information about style and markdown syntax
  • If the CI Details link gives a 404, you need to log in to readthedocs.com
• Add link to generated documentation here
  • you can find this by following the read the docs link from the CI check
• Ask for help in #documentation

Jira ticket: TODO
Link to generated documentation: TODO

[phreppo]

I think that this is missing: #335 (comment).
I did not check, but are the following addressed?

• DOC-433 | CERT-7992 | Added solana cli options #335 (comment)
• DOC-433 | CERT-7992 | Added solana cli options #335 (comment)
• DOC-433 | CERT-7992 | Added solana cli options #335 (comment)

Spell checking is failing as well.

[phreppo]

Did you try to compile the documentation with this?
I don't think it looks as expected

[yoav-el-certora]

This is what we've done in the solidity docs

Documentation/docs/prover/cli/options.md

Line 31 in 49ae6f3

(--verify)=

[yoav-el-certora]

I think that this is missing: #335 (comment). I did not check, but are the following addressed?

• DOC-433 | CERT-7992 | Added solana cli options #335 (comment)
• DOC-433 | CERT-7992 | Added solana cli options #335 (comment)
• DOC-433 | CERT-7992 | Added solana cli options #335 (comment)

Spell checking is failing as well.

Addressed comments which are relevant. Some fixes you already did in the main branch after merging the original PR.