Typo

docs/docs/getting-started/1-creating-an-aggregate-root.md

@@ -78,7 +78,7 @@ best fits your use-case. You can use UUIDs or an identifier that's
 natural to the domain you're modeling (e.g. a serial number or a unique
 group identifier).
 
-Having unique ID classes for each typea of aggregate has an added benefit
+Having unique ID classes for each type of aggregate has an added benefit
 when you're refactoring and events or commands move to a different aggregate. The 
 types will assure you're using the right kind of ID. The fact a ProductId
 and a UserID might both be UUIDs under the hood is just a coincidence,