Tenant typos

docs/design/AZURE_FEDERATIONS.md

@@ -7,7 +7,7 @@ Implementing Federations inside a new Doctrine Sharding Extension. Some extensio
 * Add support for Database Schema Operations
     * CREATE FEDERATION
     * CREATE TABLE ... FEDERATED ON
-    * Add support to create a multi-tenent schema from any given schema
+    * Add support to create a multi-tenant schema from any given schema
 * Add API to pick a shard based on distribution key and atomic value
 * Add API to ask about federations, federation members and so on.
 * Add Sharding Abstraction
@@ -17,7 +17,7 @@ Implementing Federations inside a new Doctrine Sharding Extension. Some extensio
 2. ORM (Object-Relational Mapper)
 
 * Federation Key has to be part of the clustered index of the table
-    * Test with a pure Multi-Tenent App with Filtering = ON (TaskList)
+    * Test with a pure Multi-Tenant App with Filtering = ON (TaskList)
     * Test with sharded app (Weather)
 
 ## Implementation Details

docs/design/SHARDING.md

@@ -50,7 +50,7 @@ Assumptions:
 
 ### SQL Azure Federations
 
-SQL Azure is a special case, points 1, 2, 3, 4, 7 and 8 are partly handled on the database level. This makes it a perfect test-implementation for just the subset of features in points 5-6. However there need to be a way to configure SchemaTool to generate the correct Schema on SQL Azure.
+SQL Azure is a special case, points 1, 2, 3, 4, 7 and 8 are partly handled on the database level. This makes it a perfect test-implementation for just the subset of features in points 5-6. However there needs to be a way to configure SchemaTool to generate the correct Schema on SQL Azure.
 
 * SELECT Operations: The most simple assumption is to always query all shards unless the user specifies otherwise explicitly.
 * Queries can be merged in PHP code, this obviously does not work for DISTINCT, GROUP BY and ORDER BY queries.