Update README.md to indicate explicitly that the polyfill doesn't req…

…uire monkey patching the glocal

README.md

@@ -36,12 +36,18 @@ const deserialized = deserialize(serialized);
 ```
 
 #### Global Polyfill
+Note: Only monkey patch the global if needed. This polyfill works just fine as an explicit import: `import structuredClone from "@ungap/structured-clone"`
 ```js
 // Attach the polyfill as a Global function
 import structuredClone from "@ungap/structured-clone";
 if (!("structuredClone" in globalThis)) {
   globalThis.structuredClone = structuredClone;
 }
+
+// Or don't monkey patch
+import structuredClone from "@ungap/structured-clone"
+// Just use it in the file
+structuredClone()
 ```
 
 **Note**: Do not attach this module's default export directly to the global scope, whithout a conditional guard to detect a native implementation. In environments where there is a native global implementation of `structuredClone()` already, assignment to the global object will result in an infinite loop when `globalThis.structuredClone()` is called. See the example above for a safe way to provide the polyfill globally in your project.