Update LSP-0-ERC725Account.md

[KiriKev]

• Corrected grammar, misspelling, double-blanks and punctuation marks
• Exported referencing Hyperlinks to the bottom of the document, resulting in a cleaner code
• Highlighted "lsp20VerifyCall" that should have been highlighted in the description
• Replaced "should" with "SHOULD"
• Linked "DELEGATECALL" opcode to ERC725X execute function description

Unified content:

• Filled blanks on LSP1UniversalReceiverDelegate JSON codes
• Changed LSPX to LSPX-NameOfStandard. So the reader immediately sees the standard name, that the function is taken from, which leads to a faster memorization and less friction in studying a standard.
• Overall standard definitions changed to LSPX-NameOfStandard

[KiriKev]

Done and ready for merge. And you're welcome! Glad I can help you guys 👍 I will then continue to read myself through the LSP's for the next weeks while also doing reviews here and there. Do you have specific merge-rules defined, which should apply now or can you postpone that merge for a couple more days, so I can commit a few more changes, if I'll find issues, to keep the merge-amount low?

[CJ42]

@KiriKev there is no specific rules, but the only thing I would suggest are:

• try to keep the commit history clean (avoid commits with a little change, prefer doing git commit --amend for instance.
• when you have resolved something from a reviewer, click on the "Resolve conversation" button, so that it collapses and we know you fixed it.

I will merge now.