Made note about mlAdminUsername in sample project

Author: rjrudin

examples/sample-project/gradle.properties

@@ -8,58 +8,53 @@ mlAppName=sample-project
 mlRestPort=8100
 
 # If specified, then a test database with app servers for that database will be created, which can then be used for
-# automated tests. 
+# automated tests.
 mlTestRestPort=8101
 
 # You can define just mlUsername and mlPassword, and that user will be used for all deployment operations, but that's
 # generally not a good practice, as this user will need the admin role in order to create security resources. Generally,
-# you want to use an admin user just for mlAdminUsername, as that username will only be used for creating security 
+# you want to use an admin user just for mlAdminUsername, as that username will only be used for creating security
 # resources such as users and roles. You can then use app-specific users for mlRestAdminUsername, mlManageUsername, etc.
 #
 # Otherwise, this is typically an application user. In sample-project, this user is used for running JUnit tests.
 mlUsername=sample-project-rest-admin
 mlPassword=password
 
 
-# This username/password combo is for the "REST admin" user, which is used for loading modules via the REST API as well
-# as via XCC. The user must have the rest-admin role. And in order to load modules via XCC, the user must have a role 
-# that grants xdbc:insert-in and any-uri (or some other set of URI privileges).
-# 
-# If not specified, then mlUsername/mlPassword must be used.
+# This username/password combo is for the "REST admin" user, which is used for loading modules via the REST API.
+# The user must have the rest-admin role. Non-REST API modules are loaded by default via port 8000, and this requires
+# the xdmp-eval-in privilege as well.
+#
+# If not specified, these properties default to the values of mlUsername and mlPassword.
 mlRestAdminUsername=sample-project-rest-admin
 mlRestAdminPassword=password
 
 
-# If specified, the manage username/password combo is used with the ML Management REST API for managing application 
-# resources; this user must have the manage-admin and rest-admin roles. 
-# 
+# If specified, the manage username/password combo is used with the ML Management REST API for managing application
+# resources; this user must have the manage-admin and rest-admin roles.
+#
 # If these are not set, then mlUsername/mlPassword is used for managing application resources.
 mlManageUsername=sample-project-manager
 mlManagePassword=password
 
 
-# If specified, the admin username/password combo is used with the ML Management REST API for creating users and roles. This
-# user must have the manage-admin or admin role. A good practice is to use your admin account here to create app-specific
-# users and roles, which can then be used as mlManageUsername/mlManagePassword and mlUsername/mlPassword. This practice
-# is used in this sample project; see src/main/ml-config/security to see how the app-specific users and roles are 
-# created. 
-# 
-# These properties are also used for connecting to the admin application on port 8001 - e.g. for initializing ML and for
-# waiting for ML to restart.
+# If specified, the admin username/password combo is used for operations that require connecting to the Admin server
+# on port 8001. In addition, as of version 3.2.1, this username/password combo is also used for operations on the
+# Manage server on port 8002 that require the "security" role. This may be modified in a future version of ml-gradle.
 #
-# If these properties are not set, then mlUsername/mlPassword will be used. 
+# If these properties are not set, then mlUsername/mlPassword will be used.
 mlAdminUsername=admin
 mlAdminPassword=admin
 
 
 # Configuring the number of forests for the content database (and optional test database) is a common requirement, and
-# thus there's a specific property for doing so. This is optional - if you leave it out, the content database defaults 
+# thus there's a specific property for doing so. This is optional - if you leave it out, the content database defaults
 # to 3 forests per host.
 mlContentForestsPerHost=4
 
 
-# By default, modules under /ext and /root are loaded with the default REST API asset permissions of 
-# rest-admin,read,rest-admin,update,rest-extension-user,execute. You can easily override those by setting the 
+# By default, modules under /ext and /root are loaded with the default REST API asset permissions of
+# rest-admin,read,rest-admin,update,rest-extension-user,execute. You can easily override those by setting the
 # mlModulePermissions property, as shown below. This example simply adds rest-reader/read to the set of permissions,
 # but you can customize these to be whatever you would like.
 mlModulePermissions=rest-admin,read,rest-admin,update,rest-extension-user,execute,rest-reader,read