Update Doc/library/argparse.rst

Co-authored-by: Savannah Bailey <savannahostrowski@gmail.com>

Author: hansthen

Doc/library/argparse.rst

@@ -1130,17 +1130,14 @@ Any sequence can be passed as the *choices* value, so :class:`list` objects,
 Use of :class:`enum.Enum` is not recommended because it is difficult to
 control its appearance in usage, help, and error messages.
 
-Note that inclusion in the *choices* sequence is checked after any type_
-conversions have been performed, so the type of the objects in the *choices*
-sequence should match the type_ specified. This may interfere with
-the display of the choices in usage, help and error messages, because the
-*choices* may not be familiar to the end-user.
-
-If you have to use both *type* and *choices* you can use a wrapper class
-that formats the value after type conversion back to the vocabulary of the
-end-user. However, it is usually easier to not specify *type* and perform
-type conversion in application code.
-
+Note that *choices* are checked after any type_ 
+conversions have been performed, so objects in *choices* 
+should match the type_ specified. This can make *choices* 
+appear unfamiliar in usage, help, or error messages.
+
+To keep *choices* user-friendly, consider a custom type wrapper that 
+converts and formats values, or omit type_ and handle conversion in 
+your application code.
 Formatted choices override the default *metavar* which is normally derived
 from *dest*.  This is usually what you want because the user never sees the
 *dest* parameter.  If this display isn't desirable (perhaps because there are