docs: fix typos and grammar across the developer docs

[Avicennasis]

Summary

19 verified spelling/grammar fixes across the docs and blog Markdown (18 lines, 7 files). Content only - no config, code or asset changes.

docs/student/best-practices/PaymentReversalUsingAPI.md

• will beadjusted -> will be adjusted
• using this API verses the void payment -> versus
• utilizing the these APIs -> utilizing these APIs

docs/developer-portal/creating-rest-or-lti-application.md

• **My integreaton supports LTI 1.3** -> **My integration supports LTI 1.3**
• make an old key and secret unusuable -> unusable
• using your application. this is how it looks -> This is how it looks (sentence start)
• This is how it looks like when you have already registered -> This is what it looks like ...

docs/blackboard/rest-apis/hands-on/content.md

• this is how it looks like in the GUI -> this is what it looks like in the GUI (same wording error as above)

docs/archive/b2/getting-started/rosetta-stone.md

• Was first availalbe -> available
• 9.1 Q4 2108 Cumulative Update 4 -> 9.1 Q4 2018 ... (build 3500.0.4 is the Q4 2018 line)
• 9.1 Q4 2016 Cumlative Update 3 -> Cumulative

blog/2022/2022-08-12-DevCon2022.md

• 5 classes to simpilfy -> simplify
• basic elements such API authentication -> such as API authentication
• custom tools, banner, footers, etc. -> custom tools, banners, footers, etc.

docs/blackboard/rest-apis/getting-started/lti-or-rest.md

• likley the best, way for and instructor -> likely the best, way for an instructor
• each platform has it's own nuanced way -> its

docs/blackboard/rest-apis/getting-started/framework.md

• 1. **Developer:**: This is the person -> 1. **Developer:** This is the person (doubled colon)
• any other another party -> any other party
• for a given vendors application -> for a given vendor's application

Left alone deliberately: the devcon2022-moving2ultra-phasedaoproach.pdf link, because the asset in static/assets/files/ really is named that way and changing only the reference would break the link.