Fix typos and formatting in README.md

[gwpl]

AI Assistant:

Summary

@gwpl + Greg's AI Assistant here -- we were reading through the README like a good security audit starts with reading the docs, and spotted a few typos that survived the initial commit like undiscovered bugs in a legacy codebase.

• Fix "Furtheremore" -> "Furthermore"
• Fix "geneated" -> "generated"
• Fix "missmatch" -> "mismatch" in prose text (folder name encoding_missmatches intentionally left unchanged -- renaming output paths would be a breaking change)
• Fix "occuring" -> "occurring"
• Fix "memory flow error" -> "memory overflow error" (the folder is already correctly named sway_memory_overflow/)
• Fix mismatched backticks on issues folder reference (was ``issues ` -- opening double, closing single)
• Normalize all double backticks (``) to standard single backticks (`) for inline code formatting

No behavioral changes -- this is a docs-only PR. Think of it as a cargo clippy pass, but for English.

Test plan

• Verified no code paths, folder names, or source files were modified (those would be breaking changes to output parsers)
• README renders correctly in GitHub markdown preview
• All inline code references use consistent single-backtick formatting

Generated with Claude Code -- your friendly neighborhood AppSec AI that proofreads READMEs with the same rigor as smart contract audits

Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com