diff --git a/docs/user/Embedding-Build-Tools.md b/docs/user/Embedding-Build-Tools.md
index 7bb37c0e6c..9e353ed027 100644
--- a/docs/user/Embedding-Build-Tools.md
+++ b/docs/user/Embedding-Build-Tools.md
@@ -62,10 +62,13 @@ This path must be configured identically in both your build plugin and runtime c
 
 Some files need to exist on the real filesystem rather than staying embedded as Java resources.
 
-This is required for Python C extensions (`.so`, `.dylib`, `.pyd`, `.dll`) and font files (`.ttf`) that must be accessed by the operating system loader outside the Truffle sandbox.
-GraalPy automatically extracts these file types to a temporary directory when first accessed, then delegates to the real files for subsequent operations.
+This is required for Python C extensions (`.so`, `.dylib`, `.pyd`, `.dll`) and other files that are opened directly by native libraries outside Python's file APIs.
+GraalPy automatically extracts common native library and font file types such as `.so`, `.dylib`, `.pyd`, `.dll`, and `.ttf` when first accessed, then delegates to the real files for subsequent operations.
 
-Use the `VirtualFileSystem$Builder#extractFilter` API to modify which files get extracted automatically.
+If a package reports that an embedded file under `/graalpy_vfs` does not exist, check whether a native library is opening that file directly.
+For example, packages using ONNX Runtime may need model files such as `.onnx` to be extracted as real files.
+
+Use the `VirtualFileSystem$Builder#extractFilter` API to customize which files are extracted automatically.
 For full control, extract all resources to a user-defined directory before creating your GraalPy context:
 
 - `GraalPyResources.extractVirtualFileSystemResources(VirtualFileSystem vfs, Path externalResourcesDirectory)` - Extract resources to a specified directory
diff --git a/docs/user/Interoperability.md b/docs/user/Interoperability.md
index 0c0bcb7347..2e730034be 100644
--- a/docs/user/Interoperability.md
+++ b/docs/user/Interoperability.md
@@ -340,7 +340,7 @@ Types not listed in the table below have no special interpretation in Python.
 
 | Interop Type   | Inherits from                     | Python Interpretation                                                                                               |
 | :------------- | :-------------------------------- | :------------------------------------------------------------------------------------------------------------------ |
-| `array`        | ForeignList, `list`               | An `array` behaves like a Python `list`.                                                                                                                                                                                                   |
+| `array`        | ForeignList, `list`               | An `array` behaves like a Python `list`. Just like Python lists, the size must fit into a 32-bit signed integer.                                                                                                                           |
 | `boolean`      | ForeignBoolean, ForeignNumber     | `boolean` behaves like Python booleans, including the fact that in Python, all booleans are also integers (`1` and `0` for `true` and `false`, respectively).                                                                                      |
 | `buffer`       | ForeignObject                     | Buffers work like Python buffer objects (such as those used with `memoryview`) to avoid copying data.                            |
 | `exception`    | ForeignException, `BaseException` | An `exception` can be caught in a generic `except` clause.                                                                                                                                                                                 |