fix recieved -> received typos

[prawnpie]

I noticed this while reading the docs. Figured I'd submit a PR since it's on GitHub.

[2bndy5]

LGTM. I often forget that "i before e except after c" rule unless I say it out load when I write. 😁 It would go a long way if vscode had some spell-checking for doc comments only.

[2bndy5]

These changes may not get shown in the stable release docs for a while. I'm currently trying out a different way to organize the growing list of functions.

Also, I've been working on making the doxygen HTML output material-design compatible, but I'm slowing finding out now how radically different the html generation has changed since doxygen v1.8.17 (been testing on v1.9.1)... In the end, I expect most of the HTML to get modified via JS (🤮) on-browser-load.

[prawnpie]

Thanks for merging. No worries on timing until it's in the release docs, just happy to fix it upstream so it'll eventually be sorted. Now, off to find a reputable nrf24l01 module that actually works... so many crappy clones out there. I just ordered 2 from sparkfun just to have some reference modules that I can trust. sheesh.

[2bndy5]

Power is the main problem with these modules. I think the sparkfun modules address this by integrating its own power regulator, but I have no experience with them. I recently received (yes I typed that wrong again at first) some ebyte modules that seem reliable, but those ebyte modules tend to have different power specs depending on which module model you purchase.

[2bndy5]

It would go a long way if vscode had some spell-checking for doc comments only.

I just found this extension which seems useful