Skip to content

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

fix: typos in challenges (#1257) (#1258)

Ishtiaq Ul Haq Syed1b876dfaa415
diff --git a/challenges/generic-type-arguments/prompt.md b/challenges/generic-type-arguments/prompt.md
index 02fa8151..5964029a 100644
--- a/challenges/generic-type-arguments/prompt.md
+++ b/challenges/generic-type-arguments/prompt.md
@@ -66,7 +66,7 @@ type GroceryItem<Name, Price, InStock> = {
};
```
-Now you can change pass arguments to this type:
+Now you can pass arguments to this type:
```ts
type AvocadoToast = GroceryItem<'Avocado Toast', 12.99, true>;
diff --git a/challenges/mapped-object-types/prompt.md b/challenges/mapped-object-types/prompt.md
index 16cda742..aaa6aab3 100644
--- a/challenges/mapped-object-types/prompt.md
+++ b/challenges/mapped-object-types/prompt.md
@@ -43,7 +43,7 @@ Let's talk about what this syntax does, piece by piece:
- `;` it might at first seem strange, but if you take a step back, this is just a `property: value` line in an object type, so we end it with a semicolon like we normally would with types in TypeScript.
- `};` ends the type declaration.
-But, all this _stuff_ but we end up with a type that's literally identical to what we started with. In the above code, `Example` and `MoviesByGenre` are literally the same type to TypeScript because TypeScript is a structural type system. They have all the same properties and values, so to TypeScript they are basically aliases at this point (aliases with extra steps, granted!).
+But, all this _stuff_, and we end up with a type that's literally identical to what we started with. In the above code, `Example` and `MoviesByGenre` are literally the same type to TypeScript because TypeScript is a structural type system. They have all the same properties and values, so to TypeScript they are basically aliases at this point (aliases with extra steps, granted!).
### Resetting all values