Teeny Tiny Typos <3

[JayeVAJohnson]

Hi,

I'm sharing these because it was requested in your literature, it's great practice for me, and this content is so helpful, so I want to respond in kind.

If nothing was ever changed, I would still be exceedingly grateful for this content.

These are just some noticings:

1. On this page:

http://ada-developers-academy.github.io/ada-build/learning-at-ada/ada-languages

The paragraph as it reads below is missing the word "to" or a similar sentiment:

"ReactJS
ReactJS is a JavaScript framework for building user interfaces. React allows front-end developers organize their application and provide quick and powerful single-page-applications (SPAs)."

2. On this page:

http://ada-developers-academy.github.io/ada-build/learning-at-ada/problem-solving/algorithms.html

The bottom 2 paragraphs read:

"Even if the instructions worked for one particular case, we should consider how the algorithm would fair..." and I believe here, the correct usage would be the similar word "fare."

Next paragraph:

"Often times some of our test cases fail or our desired output is reached but not in the most efficient way possible..." I believe it is "Oftentimes."
Here's a source with more information about that:

https://writingexplained.org/often-times-or-oftentimes-difference

3. Regarding the Optional reading, "What is a Good Test Case," the Kaner article contains a broken link.

I found this link via Google Scholar. It may be something that y'all wish to archive on your own server if that could possibly be permissible, so that the link is perhaps more evergreen:

https://www.techwell.com/sites/default/files/articles/XDD6505filelistfilename1_0.pdf

The article's so helpful. I appreciate it.

[I have since learned this was shared prior as a pull request:
https://github.com//pull/275]

Just so that I'm not inundating y'all with tons of new issue tickets, I'll update issue tickets no more than once per day. If I happen to see something, I'll just update that day's ticket.

Respectfully,

Jaye