Remove redundant text in user.name description. All text fields are k…

…eyword now.

README.md

@@ -402,7 +402,7 @@ Note also that the `user` fields may be used directly at the top level.
 | Field  | Description  | Level  | Type  | Example  |
 |---|---|---|---|---|
 | <a name="user.id"></a>user.id | One or multiple unique identifiers of the user. | core | keyword |  |
-| <a name="user.name"></a>user.name | Programmatic name / login of the user.<br/>The field is a keyword, and will not be tokenized. | core | keyword | `albert` |
+| <a name="user.name"></a>user.name | Programmatic name / login of the user. | core | keyword | `albert` |
 | <a name="user.full_name"></a>user.full_name | User's full name, if available. | extended | keyword | `Albert Einstein` |
 | <a name="user.email"></a>user.email | User email address. | extended | keyword |  |
 | <a name="user.hash"></a>user.hash | Unique user hash to correlate information for a user in anonymized form.<br/>Useful if `user.id` or `user.name` contain confidential information and cannot be used. | extended | keyword |  |

fields.yml

@@ -1227,8 +1227,6 @@
           description: >
             Programmatic name / login of the user.
     
-            The field is a keyword, and will not be tokenized.
-
         - name: full_name
           level: extended
           type: keyword

schemas/user.yml

@@ -29,8 +29,6 @@
       description: >
         Programmatic name / login of the user.
 
-        The field is a keyword, and will not be tokenized.
-
     - name: full_name
       level: extended
       type: keyword