This PR includes the following:
- Fix issue with daemon-rpc example styling.
- Remove references to deprecated class “cli-code” and replace with
code blocks where necessary.
- Add new line between all RPC calls and outputs.
- Use 3-apostrophe code blocks instead of indent for all curl examples
for markdown neatness and to enable future syntax highlighting.
The proper CSS class was changed from "accordian" to "accordion". The "If Monero is so private how do we know they're not being created out of thin air?" section got left out when the change was made which results in the ugly default checkbox being used instead of rehrar's custom CSS
Monero is secure
Do we really want the first sentence about the security of Monero to include "extremely difficult to hack and steal your funds. " To me that doesn't sound safe for large amounts if it's only "extremely difficult"... and why mention "hack" and "steal" at all? Further, if you are trying to define "decentralized cryptocurrency" the definition is absolutely NOT "extremely difficult to hack and steal your funds.". You could say the same of cash in a bank vault, an ATM machine, a centralized currency, or the safe in my basement... Those are all "extremely difficult to hack and steal" from. It seems to me we should be explaining what decentralized cryptocurrency is and perhaps stating it's the safest method known to mankind to store value, outside of Fort Knox. Not that its hard to hack and steal!
Monero is fungible - if we're going to say it's untraceable above, we may as well remove the whole "In its current state, it is extremely unlikely that Monero will ever be..." and just bluntly state that it will never be blacklisted due to previous association. Also, very few people know what fungible even means, so I have added the definition so people know what they're reading.
