Delete instances of Sandbox

content/en/docs/howto10/extensibility/build-javascript-actions/create-native-javascript-action.md

@@ -155,7 +155,7 @@ To make the nanoflow shown above, do the following:
 1. Connect the **Read NFC Tag** activity with a **Show message** activity. Right-click the connection to the **Show message** action and select **Set as error handler**.
 1. Connect this **Show message** action to an end point. Set the type as information, and set the template as *Your NFC tags says: {1}*. Use *$TagValue* as a parameter.
 1. Optionally you can add **Show progress** and **Hide progress** activities to give your user more information while using the NFC reader. This action can be found in the **Nanoflow Commons** module.
-1. Deploy your app to the sandbox.
+1. Deploy your app.
 
 ### Writing an NFC Tag {#write-nfc-tag}
 

content/en/docs/howto9/extensibility/build-javascript-actions/create-native-javascript-action.md

@@ -155,7 +155,7 @@ To make the nanoflow shown above, do the following:
 1. Connect the **Read NFC Tag** activity with a **Show message** activity. Right-click the connection to the **Show message** action and select **Set as error handler**.
 1. Connect this **Show message** action to an end point. Set the type as information, and set the template as *Your NFC tags says: {1}*. Use *$TagValue* as a parameter.
 1. Optionally you can add **Show progress** and **Hide progress** activities to give your user more information while using the NFC reader. This action can be found in the **Nanoflow Commons** module.
-1. Deploy your app to the sandbox.
+1. Deploy your app.
 
 ### Writing an NFC Tag {#write-nfc-tag}
 

content/en/docs/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/local-data-security.md

@@ -13,7 +13,7 @@ Offline-first apps built with Mendix store data in the local database to provide
 
 ## Local Data Safety
 
-In native mobile apps, the Mendix Client stores the data and files in the file system—often sandboxed and encrypted by the operating system. This ensures that other apps, external entities, or end-users cannot access the app's data. 
+In native mobile apps, the Mendix Client stores the data and files in the file system—often walled-off and encrypted by the operating system. This ensures that other apps, external entities, or end-users cannot access the app's data. 
 
 Data stored in a Mendix app is excluded from standard backup mechanisms to prevent data from leaking outside the app's boundaries. However, the built-in mechanisms can be bypassed in cases where the operating system is compromised, such as rooting an Android device.
 

content/en/docs/refguide9/mobile/building-efficient-mobile-apps/offlinefirst-data/local-data-security.md

@@ -13,7 +13,7 @@ Offline-first apps built with Mendix store data in the local database to provide
 
 ## Local Data Safety
 
-In native mobile apps, the Mendix Client stores the data and files in the file system—often sandboxed and encrypted by the operating system. This ensures that other apps, external entities, or end-users cannot access the app's data. 
+In native mobile apps, the Mendix Client stores the data and files in the file system—often walled-in and encrypted by the operating system. This ensures that other apps, external entities, or end-users cannot access the app's data. 
 
 Data stored in a Mendix app is excluded from standard backup mechanisms to prevent data from leaking outside the app's boundaries. However, the built-in mechanisms can be bypassed in cases where the operating system is compromised, such as rooting an Android device.
 

content/en/docs/releasenotes/studio-pro/9/9.20.md

@@ -37,7 +37,7 @@ weight: 80
 * We made all properties dialog boxes resizable.
 * The **Send** and **Delete external object** activities now use the `Accept-Language` HTTP header to communicate the user's preferred language to the server.
 * Validation feedback from OData's insert, update, and delete microflows is now translated into the language provided in `Accept-Language`.
-* The example URL for published OData services and web services is now the sandbox cloud URL when the app is running there.
+* The example URL for published OData services and web services is now the cloud URL when the app is running there.
 * In published OData services, the list of entities and the list of entity details now have the same width.
 * We improved the alignment of the controls on the **Published OData Resource** dialog box.
 * We added more control to the **Show user task page** microflow activity and button. It is now possible to configure if the activity should automatically assign the current user to the task. Secondly, you can now control who is allowed to open the task page when a task is already assigned (only the user currently assigned or all users with access to the task).