Jira documentation on managing multiple user directories has inaccurate example

Please see https://confluence.atlassian.com/adminjiraserver074/managing-multiple-directories-881683376.html
The specific problem is near the bottom of this page where it cites Example #2

Updating Users and groups

If you update a user or group via the application's administration screens, the update will be made in the first directory where the application has write permissions.

Example 1:

• You have connected two directories: The Customers directory and the Partners directory.
• The application has permission to update both directories.
• The Customers directory is first in the directory order.
• A username jsmith exists in both the Customers directory and the Partners directory.
• You update the email address of user jsmith via the application's administration screens.
• The email address will be updated in the Customers directory only, not the Partners directory.

Example 2:

• You have connected two directories: A read/write LDAP directory and the internal directory.
• The LDAP directory is first in the directory order.
• All new users will be added to the LDAP directory. It is not possible to add a new user to the internal directory.

I believe that the very last line is actually inaccurate now in all current versions of Jira Server.  You can in fact create a new user in either directory type in this configuration.   The document is indicating that this is not possible to create in the internal directory when in fact it is.

I suspect that this might have been true at the time this document was created.   I did come across this feature request that was implemented in Jira 5.0 https://jira.atlassian.com/browse/JRASERVER-11322 to allow for managing accounts from different user directories.  I think this would have been necessary for the current functionality.  

I'm not sure though how to best address this issue, perhaps completely removing example #2 would be best here.   I still believe that Example #1 is still valid in Jira, but perhaps this would require a technical review to make sure this document is accurate for modern Jira versions.