docs(guide): Fix live-preview breaking in DataPipelines guide (#9552)

Author: tobiu

learn/guides/datahandling/DataPipelines.md

@@ -128,7 +128,7 @@ Because RPC and local fetching now share the same architecture, integrating a We
 
 If your project defines an RPC API (via `remotes-api.json`), you don't even need to define the connection manually. You just reference the API endpoint, and the system dynamically constructs the WebSocket pipeline for you.
 
-```javascript live-preview
+```javascript readonly
 import Container from '../../src/container/Base.mjs';
 import Model     from '../../src/data/Model.mjs';
 import Store     from '../../src/data/Store.mjs';
@@ -192,4 +192,4 @@ If you are upgrading from an older version of Neo.mjs, your existing `url` and `
 *   **Legacy `url`:** If you define `url: 'data.json'`, the Store automatically creates a Pipeline using `connection-xhr` behind the scenes.
 *   **Legacy `api`:** If you define `api: 'MyService'`, the Store resolves the API definition and builds the appropriate Pipeline (Fetch, Xhr, or WebSocket) dynamically.
 
-However, to unlock advanced features like Data Worker offloading (`workerExecution: 'data'`) or custom Parsers, you must switch to explicitly defining the `pipeline` config block.
+However, to unlock advanced features like Data Worker offloading (`workerExecution: 'data'`) or custom Parsers, you must switch to explicitly defining the `pipeline` config block.