Clarifying Documentation Through Corrections in Code Comments

[joaolago1113]

I've made a few small fixes in the code. These changes will make things clearer and more professional.
Here's what I've done:

1. Commit 1510c48: Fixed a spelling mistake - 'occurences' to 'occurrences'.
2. Commit 2dd6575: Changed 'proogs' to 'proofs'.
3. Commit 6467072: Corrected 'it's purpose' to 'its purpose'.
4. Commit 62ee7f0: Fixed 'profiile' to 'profile'.
5. Commit 66596e9: Updated 'encoutering' to 'encountering'.
6. Commit 8ce301e: Changed 'overhide' to 'override' and 'accross' to 'across'.
7. Commit 7aa874f: Tweaked an error message to make it clearer.
8. Commit b107688: Fixed a confusing part where 'doesn't not' should be 'does not'.
9. Commit 62d1f4c: Corrected 'methdods' to 'methods'.

The fix in commit b107688 is important because it was misleading before with the double negative "doesn't not", please check that the correct way is "does not".

[CLAassistant]

All committers have signed the CLA.

[gbotrel]

Thanks for the PR. However, we decided to close PRs with formatting / typo fixes only at the moment (as per the CONTRIBUTING.md).