Connector info should reflect this as well

Author: wied03

astro/src/content/docs/lifecycle/migrate-users/connectors/index.mdx

@@ -61,12 +61,12 @@ The user will be placed into the same tenant as the application they are authent
 
 If you are authenticating a user, you must provide the following fields in the user object you return.
 
-* `user.username` or `user.email`
+* `user.username`, `user.email`, or `user.phoneNumber`
 * `user.id`: a FusionAuth compatible UUID
 
 If you are using the generic connector, you are building the `user` object, so ensure these fields are in the JSON. If you are using the LDAP connector, make sure you set these fields in the configured LDAP Reconcile lambda.
 
-In addition, ensure that the same `user.id` is returned each time a user is retrieved. If you have an LDAP attribute in the form of a UUID or a value that can be translated to a UUID, using that attribute or its translation is recommended. If you have to generate a UUID, ensure that you are able to return the same value each time the user authenticates. Doing so ensures that FusionAuth knows which user is being referenced, even if the username or email address changes.
+In addition, ensure that the same `user.id` is returned each time a user is retrieved. If you have an LDAP attribute in the form of a UUID or a value that can be translated to a UUID, using that attribute or its translation is recommended. If you have to generate a UUID, ensure that you are able to return the same value each time the user authenticates. Doing so ensures that FusionAuth knows which user is being referenced, even if the username, email address, or phone number changes.
 
 ### Suggested Fields