Update server-level-roles.md

Author: shohamMSFT

docs/relational-databases/security/authentication-access/server-level-roles.md

@@ -70,7 +70,7 @@ The following table shows fixed server-level roles introduced in [!INCLUDE [sssq
 | --- | --- |
 | `##MS_DatabaseConnector##` | Members of the `##MS_DatabaseConnector##` fixed server role can connect to any database without requiring a User-account in the database to connect to.<br /><br />To deny the `CONNECT` permission to a specific database, users can create a matching user account for this login in the database and then `DENY` the `CONNECT` permission to the database-user. This `DENY` permission overrules the `GRANT CONNECT` permission coming from this role. |
 | `##MS_LoginManager##` | Members of the `##MS_LoginManager##` fixed server role can create, delete, and modify logins. Contrary to the old fixed server role **securityadmin**, this role doesn't allow members to `GRANT` privileges. It's a more limited role that helps to comply with the *Principle of least Privilege*. |
-| `##MS_DatabaseManager##` | Members of the `##MS_DatabaseManager##` fixed server role can create and delete databases. A member of the `##MS_DatabaseManager##` role that creates a database, becomes the owner of that database, which allows that user to connect to that database as the `dbo` user. The `dbo` user has all database permissions in the database. Members of the `##MS_DatabaseManager##` role don't necessarily have permission to access databases that they don't own. This server role has the same privileges as the **dbcreator** role in SQL Server, but we recommend using this new role over the former, since this role exists also in Azure SQL Database and thus helps using the same scripts across different environments. |
+| `##MS_DatabaseManager##` | Members of the `##MS_DatabaseManager##` fixed server role can create and delete databases. A member of the `##MS_DatabaseManager##` role that creates a database, becomes the owner of that database, which allows that user to connect to that database as the `dbo` user. The `dbo` user has all database permissions in the database. Members of the `##MS_DatabaseManager##` role don't necessarily have permission to access databases that they don't own. This server role has the same privileges as the **dbcreator** role in SQL Server, but we recommend using this new role over the former, since this role exists also in Azure SQL Database and thus helps using the same scripts across different environments. <br /><br /> Members of this role can potentially elevate their privileges under certain conditions. It is strongly recommended to apply the principle of least privilege when assigning this role and to monitor all activity performed by its members. |
 | `##MS_ServerStateManager##` | Members of the `##MS_ServerStateManager##` fixed server role have the same permissions as the `##MS_ServerStateReader##` role. Also, it holds the `ALTER SERVER STATE` permission, which allows access to several management operations, such as: `DBCC FREEPROCCACHE`, `DBCC FREESYSTEMCACHE ('ALL')`, `DBCC SQLPERF()` |
 | `##MS_ServerStateReader##` | Members of the `##MS_ServerStateReader##` fixed server role can read all dynamic management views (DMVs) and functions that are covered by `VIEW SERVER STATE`, and respectively has `VIEW DATABASE STATE` permission on any database on which the member of this role has a user account. |
 | `##MS_ServerPerformanceStateReader##` | Members of the `##MS_ServerPerformanceStateReader##` fixed server role can read all dynamic management views (DMVs) and functions that are covered by `VIEW SERVER PERFORMANCE STATE`, and respectively has `VIEW DATABASE PERFORMANCE STATE` permission on any database on which the member of this role has a user account. Subset of what the `##MS_ServerStateReader##` server role has access to, which helps to comply with the *Principle of least Privilege*. |