Typos, round 8

[Firsh]

https://www.totaltypescript.com/workshops/typescript-pro-essentials/the-weird-parts-of-typescript/excess-property-warnings-in-typescript/exercise

"In this exercise, we're dealing with an options object along FetchOptions"... -> along with

---

https://www.totaltypescript.com/workshops/typescript-pro-essentials/the-weird-parts-of-typescript/excess-properties-in-functions/exercise

..."this challenge--try to find both!" -> double dash not converted to em dash (—)

---

https://www.totaltypescript.com/workshops/typescript-pro-essentials/the-weird-parts-of-typescript/objectkeys-and-objectentries-in-typescript

Missing `` around the word string here:
"we end up with a key of string and a value of any"

---

https://www.totaltypescript.com/workshops/typescript-pro-essentials/the-weird-parts-of-typescript/iterating-over-object-keys-in-typescript/solution

"is a like a more precise string." -> is like a...

---

https://www.totaltypescript.com/workshops/typescript-pro-essentials/the-weird-parts-of-typescript/typing-functions-with-object-params/solution

..."the func's type has changed a single function that takes in"... -> changed to a / changed into a

"potential inputs– in this case" -> use em dash — with symmetrical space around it

"functions in JavaScript– They simply" -> They should be lowercase and use em dash — with symmetrical space around it

---

https://www.totaltypescript.com/workshops/typescript-pro-essentials/the-weird-parts-of-typescript/properly-typing-an-object-of-functions/solution

"In order to resolve the error at on the type level, we need to add a type assertion to input." -> use either at or on [the type level]