Apply suggestions from code review

Author: v-albemi

docs/relational-databases/security/authentication-access/ownership-and-user-schema-separation.md

@@ -1,5 +1,5 @@
 ---
-title: "Ownership and User-Schema Separation in SQL Server"
+title: "Ownership and user-schema separation in SQL Server"
 description: Learn how user-schema separation allows flexibility in managing SQL Server database object permissions. Schemas group objects into separate namespaces. 
 ms.date: "08/02/2021"
 ms.prod: sql
@@ -9,11 +9,11 @@ ms.reviewer: vanto
 author: AndreasWolter
 ms.author: anwolter
 ---
-# Ownership and User-Schema Separation in SQL Server
+# Ownership and user-schema separation in SQL Server
 
 A core concept of SQL Server security is that owners of objects have irrevocable permissions to administer them. You can't remove privileges from an object owner, and you can't drop users from a database if they own objects in it.  
 
-## User-Schema Separation  
+## User-schema separation  
 
  User-schema separation allows for more flexibility in managing database object permissions. A *schema* is a named container for database objects, which allows you to group objects into separate namespaces. For example, the AdventureWorks sample database contains schemas for Production, Sales, and HumanResources.  
 
@@ -23,13 +23,13 @@ A core concept of SQL Server security is that owners of objects have irrevocable
 Server.Database.DatabaseSchema.DatabaseObject  
 ```  
 
-### Schema Owners and Permissions  
+### Schema owners and permissions  
 
  Schemas can be owned by any database [principal](../authentication-access/principals-database-engine.md), and a single principal can own multiple schemas. You can apply security rules to a schema, which are inherited by all objects in the schema. Once you set up access permissions for a schema, those permissions are automatically applied as new objects are added to the schema. Users can be assigned a default schema, and multiple database users can share the same schema.  
 
  By default, when developers create objects in a schema, the objects are owned by the security principal that owns the schema, not the developer. Object ownership can be transferred with [ALTER AUTHORIZATION Transact-SQL](../../../t-sql/statements/alter-authorization-transact-sql.md) statement. A schema can also contain objects that are owned by different users and have more granular permissions than those assigned to the schema, although this isn't recommended because it adds complexity to managing permissions. Objects can be moved between schemas, and schema ownership can be transferred between principals. Database users can be dropped without affecting schemas.  
 
-### Built-In Schemas for backward compatibility 
+### Built-in schemas for backward compatibility 
 
  SQL Server ships with nine pre-defined schemas that have the same names as the built-in database users and roles: *db_accessadmin, db_backupoperator, db_datareader, db_datawriter, db_ddladmin, db_denydatareader, db_denydatawriter, db_owner, db_securityadmin*. These exist for backward compatibility. The recommendation is to not use them for user objects. You can drop the schemas that have the same names as the fixed database roles - unless they're already in use, in which case the drop-command will simply return an error and block the drop of the used schema.
 
@@ -83,7 +83,7 @@ The following schemas cannot be dropped:
 > [!NOTE]
 > The `sys` and `INFORMATION_SCHEMA` schemas are reserved for system objects. You cannot create objects in these schemas and you cannot drop them.  
   
-#### The dbo Schema  
+#### The dbo schema  
 
  The `dbo` schema is the default schema of every database. By default, users created with the CREATE USER Transact-SQL command have `dbo` as their default schema. The `dbo` schema is owned by the `dbo` user account. 
 
@@ -92,7 +92,7 @@ The following schemas cannot be dropped:
 > [!NOTE]
 > When database objects are referenced by using a one-part name, SQL Server first looks in the user's default schema. If the object is not found there, SQL Server looks next in the `dbo` schema. If the object is not in the `dbo` schema, an error is returned.  
   
-## External Resources  
+## External resources  
 
  For more information on object ownership and schemas, see the following resources.