fix: update descriptions of the user deletion endpoint (box/box-openapi#562)

Author: box-sdk-build

.codegen.json

@@ -1 +1 @@
-{ "engineHash": "7c94f4f", "specHash": "1715587", "version": "10.0.1" }
+{ "engineHash": "7c94f4f", "specHash": "a646ae6", "version": "10.0.1" }

docs/users.md

@@ -189,9 +189,9 @@ Returns the updated user object.
 
 ## Delete user
 
-Deletes a user. By default this will fail if the user
-still owns any content. Move their owned content first
-before proceeding, or use the `force` field to delete
+Deletes a user. By default, this operation fails if the user
+still owns any content, was recently active, or recently joined the enterprise from a free account.
+To proceed, move their owned content first, or use the `force` parameter to delete
 the user and their files.
 
 This operation is performed by calling function `deleteUserById`.

src/managers/users.ts

@@ -595,8 +595,8 @@ export interface DeleteUserByIdQueryParams {
    * the deletion. */
   readonly notify?: boolean;
   /**
-   * Whether the user should be deleted even if this user
-   * still own files. */
+   * Specifies whether to delete the user even if they still own files,
+   * were recently active, or recently joined the enterprise from a free account. */
   readonly force?: boolean;
 }
 export class DeleteUserByIdHeaders {
@@ -933,9 +933,9 @@ export class UsersManager {
     };
   }
   /**
-     * Deletes a user. By default this will fail if the user
-     * still owns any content. Move their owned content first
-     * before proceeding, or use the `force` field to delete
+     * Deletes a user. By default, this operation fails if the user
+     * still owns any content, was recently active, or recently joined the enterprise from a free account.
+     * To proceed, move their owned content first, or use the `force` parameter to delete
      * the user and their files.
      * @param {string} userId The ID of the user.
     Example: "12345"