fixed spellings and grammatical mistakes

[pwnmeow]

i am onto fixing all the spelling mistakes in owasp cheatsheet project please run a diff bw old doc and my doc youll see a lot of changes git unfortunately isnt showing bcoz I copied the raw and used Grammarly and other tools to check for errors and then re-pasted the fixed version

Thank you for submitting a Pull Request (PR) to the Cheat Sheet Series.

🚩 If your PR is related to grammar/typo mistakes, please double check the file for other mistakes in order to fix all the issue on the current cheat sheet.

Please make sure that for your contribution:

• In case of a new Cheat Sheet, you have used the Cheat Sheet template.
• All the markdown files do not raise any validation policy violation, see policy here.
• All the markdown files follow these format rules.
• All your assets are stored in the assets folder.
• All the images used are in the PNG format.
• Any references to website have been formatted as TEXT
• You verified/tested the effectiveness of your contribution (e.g.: defensive code proposed is really an effective remediation? Please verify it works!).
• The CI build of your PR pass, see the build status here.

If your PR is related to an issue. Please end your PR text with the following line:

This PR covers issue #.

Thank you again for your contribution 😃

[rbsec]

Many of these changes are good, but I've made comments on some that need looking at again. Please be very careful running automated grammar checkers and make sure you're manually verifying the results - because some of the changes suggested are incorrect, and some of them are changing the actual meaning of sentences.

Grammar tools tend to be a bit unreliable for technical content, as we often use words in ways that don't quite match normal english grammar.

[pwnmeow]

let me redo it all it seems like there was a mistake of versions i pasted vs what i fixed

[mackowski]

@sheerazali19 can you please introduce changes requested by @jsoref and @rbsec?

[pwnmeow]

Yes i will

…

On Thu, 24 Oct, 2019, 4:54 PM mackowski, ***@***.***> wrote: @sheerazali19 <https://github.com/sheerazali19> can you please introduce changes requested by @jsoref <https://github.com/jsoref> and @rbsec <https://github.com/rbsec>? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#243?email_source=notifications&email_token=ACSJDUT2NAK7UQDWVQM4PSLQQGAWVA5CNFSM4I5FLI32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECEV3NA#issuecomment-545873332>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACSJDUSSQLP6XJ4MZK7ZR2LQQGAWVANCNFSM4I5FLI3Q> .

[pwnmeow]

Couldn't find time had a tight schedule and deadlines to meet

…

On Thu, 24 Oct, 2019, 5:18 PM Sheeraz Ali, ***@***.***> wrote: Yes i will On Thu, 24 Oct, 2019, 4:54 PM mackowski, ***@***.***> wrote: > @sheerazali19 <https://github.com/sheerazali19> can you please introduce > changes requested by @jsoref <https://github.com/jsoref> and @rbsec > <https://github.com/rbsec>? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#243?email_source=notifications&email_token=ACSJDUT2NAK7UQDWVQM4PSLQQGAWVA5CNFSM4I5FLI32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECEV3NA#issuecomment-545873332>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACSJDUSSQLP6XJ4MZK7ZR2LQQGAWVANCNFSM4I5FLI3Q> > . >

[mackowski]

No problem :) I just wanted to check the status.

[rbsec]

@mackowski @ThunderSon I've fixed the open comments on this by pushing to @sheerazali19's branch - so this should be good to merge now.

[ThunderSon]

This PR should be ready to merge, all review comments have been tackled.

[mackowski]

Thank you @ThunderSon for updating this PR!