JOSS style suggestions

Important

this issue only applies to the paper-joss branch from !210.

• Replace italics with bold face (with this font, italics do not stand out)
• Summary:
  • Encode: mention prime field F and why use a sophisticated prime field
  • Verify: extend "without requiring..." with something about how identifying corrupted shards allows to make only strictly additional shards lookups and only one decode
  • Yes, mention Merkle and Fiat-Shamir
• General flow notations:
  • Describe F
  • Introduce 2 sides: sender/receiver or producer/consumer
  • On the receiver/consumer side:
    • use (bj*) as received blocks, and describe that in the text
    • add (bj) as the result of verify applied to (bj*): (bj) are the valid received blocks
    • replace (si~) by (si) in the scheme (I guess they are the same)
• Remove notes:
  • 1st note: transform in a "Recoding flow with Semi-AVID", including a new scheme and notations
  • 2nd note: not really useful, can be simply removed
  • 3rd note: if the CLI app is really useful, move this to something more visible, either as a paragraph with examples, or as a key point in the statement of need
• Examples:
  • Indent code one level (to distinguish it from surrounding text)
  • Rephrase both final assertions with a received_blocks variable and k valid received blocks in the text, so that the example makes more sense with a "receiving side"
• Measurements: how many runs?
• Quality control: shorten and make it direct (no "please")
• Figures: enlarge all inner labels (axis, legends, values) so that they're the size of the main text
• System requirements: as an example, give the details of the configuration used for figs 1 and 2