Ericwang

[ewang8]

• [y ] Are the audience and objective of the document clear? E.g. a document for developers that should teach them about transaction fees.
• [y ] Is the writing:
  • Clear: No jargon.
  • Precise: No ambiguous meanings.
  • Concise: Free of superfluous detail.
• [y ] Does it follow our style guide?
• [ y] If this is a new page, does the PR include the appropriate infrastructure, e.g. adding the page to a sidebar?
• [y] Build the page (TODO link section with instructions). Does it render properly? E.g. no funny lists or formatting.
• [y] Do links go to rustdocs or devhub articles rather than code?
• [y] If this PR addresses an issue in the queue, have you referenced it in the description?

[maxsupera]

i moved the changes to another branch and made a few small fixes. closing this in favor of #30 .