Skip to content

Connect, collaborate, and grow with a community of TypeScript developers

fix lints / typos in prompt (#1160)

Heath Henleyac53184b0960
diff --git a/challenges/primitive-data-types/prompt.md b/challenges/primitive-data-types/prompt.md
index 09f2fa41..ce392c45 100644
--- a/challenges/primitive-data-types/prompt.md
+++ b/challenges/primitive-data-types/prompt.md
@@ -1,6 +1,6 @@
## The Problem Primitive Data Types Solve
-Because the ability to create primitive types are the foundational idea behind TypeScript, asking what problem primitive types solve is more like asking "what problem does _TypeScript_ solve".
+Because the ability to create primitive types is the foundational idea behind TypeScript, asking what problem primitive types solve is more like asking "what problem does _TypeScript_ solve".
TypeScript is like a really really smart spellchecker. It helps you work faster when you're at your best, but it also saves you from misspelling words when you're under stress at 3am the night before a big term paper is due.
@@ -33,7 +33,7 @@ Here are some of the basic types:
- `number`: since JavaScript only has one real number type (IEEE-754 64-bit floating point numbers), so too does TypeScript then not define types like `short` and `long` or types like `uint32` or `uint16` like you might be used to in other languages. Instead we just use `number` for everything.
- `string`: a variable length set of characters (UTF-16).
- `boolean`: Don't let this next sentence keep you up at night if it sounds strange, but just keep in the back of your mind that boolean isn't actually a primitive type deep down in TypeScript internals. It's a little different from string or number since it is just an alias for the union of `true` and `false`. It doesn't _widen_ like `number` and `string` do, and thus is slightly inconsistent. If that didn't make sense to you right now don't worry. This problem almost never surfaces in a way that's problematic so you're clear to just consider it a primitive type. Also, the way TypeScript handles `boolean` is actually the more correct way to model things from a ["Set theory"](https://en.wikipedia.org/wiki/Set_theory) standpoint.
-- `null`: this is technically really a "literal type", but it refers to the type of the `null` value in JavaScript. Since `null` is special, it get's its own type.
+- `null`: this is technically really a "literal type", but it refers to the type of the `null` value in JavaScript. Since `null` is special, it gets its own type.
- `undefined`: same as with `null`. This is a specific JavaScript value and it has a corresponding TypeScript type.
Then we've got some more advanced ones that you don't need to worry about quite yet. But here they are as a teaser: