docs: Update documentation (box/box-codegen#860) (#1112)

Author: box-sdk-build

.codegen.json

@@ -1 +1 @@
-{ "engineHash": "733e376", "specHash": "fa34496", "version": "10.0.1" }
+{ "engineHash": "48e5311", "specHash": "fa34496", "version": "10.0.1" }

docs/working-with-nulls.md

@@ -1,10 +1,10 @@
-# Handling null values in v10 version of Box Node SDK
+# Handling null values in Box Node SDK
 
-While using v10 version of Box Node SDK it's important to understand how null values behave. This document provides a general overview of null value behaviour in v10 version of box-node-sdk to help developers manage data consistently and predictably.
+While using Box Node SDK it's important to understand how null values behave. This document provides a general overview of null value behaviour in box-node-sdk to help developers manage data consistently and predictably.
 
 ## Understanding null behaviour
 
-The v10 version of Box Node SDK follows a consistent pattern when handling null values in update operations. This behaviour applies to most endpoints that modify resources such as users, files, folders and metadata. The updating field behaves differently depending on weather you omit it, set it to null, or provide a value:
+The Box Node SDK follows a consistent pattern when handling null values in update operations. This behaviour applies to most endpoints that modify resources such as users, files, folders and metadata. The updating field behaves differently depending on weather you omit it, set it to null, or provide a value:
 
 - Omitting the field: The field won't be included in request and the value will remain unchanged
 - Setting it to null: Setting a field to null, will cause sending HTTP request with field value set to null, what will result in removing its current value or disassociates it from the resource.