diff --git a/docs/en/Specifications.md b/docs/en/Specifications.md
index a9aeb2b050..2ef9c4496e 100644
--- a/docs/en/Specifications.md
+++ b/docs/en/Specifications.md
@@ -246,7 +246,7 @@ So, what's the point of a specification? Why and when should we consider to use
 
 Some benefits of using specifications:
 
-- **Reusabe**: Imagine that you need the Premium Customer filter in many places in your code base. If you go with expressions and do not create a specification, what happens if you later change the "Premium Customer" definition? Say you want to change the minimum balance from $100,000 to $250,000 and add another condition to be a customer older than 3 years. If you'd used a specification, you just change a single class. If you repeated (copy/pasted) the same expression everywhere, you need to change all of them.
+- **Reusable**: Imagine that you need the Premium Customer filter in many places in your code base. If you go with expressions and do not create a specification, what happens if you later change the "Premium Customer" definition? Say you want to change the minimum balance from $100,000 to $250,000 and add another condition to be a customer older than 3 years. If you'd used a specification, you just change a single class. If you repeated (copy/pasted) the same expression everywhere, you need to change all of them.
 - **Composable**: You can combine multiple specifications to create new specifications. This is another type of reusability.
 - **Named**: `PremiumCustomerSpecification` better explains the intent rather than a complex expression. So, if you have an expression that is meaningful in your business, consider using specifications.
 - **Testable**: A specification is a separately (and easily) testable object.