docs: fix stale lazy and middleware anchors

src/routes/solid-router/(4)advanced-concepts/(0)preloading.mdx

@@ -41,4 +41,4 @@ Calling both the route preload and the nested component preload can keep large d
 Balancing manual preloading requires observing real user flows so you avoid prefetching large bundles that the user never requests.
 Profiling tools help you spot whether preloading reduces long tasks or simply shifts work earlier without net gains.
 
-To learn more about lazy loading components, see the [lazy documentation](/reference/component-apis/lazy#preloading-data-in-nested-lazy-components).
+To learn more about lazy loading components, see the [lazy documentation](/reference/component-apis/lazy#preloading-nested-lazy-components).

src/routes/solid-start/v2/(2)guides/(0)security.mdx

@@ -46,7 +46,7 @@ If you want to use a [strict CSP](https://developer.mozilla.org/en-US/docs/Web/H
 
 1. Create middleware that generates a nonce and configures the CSP header before calling `next()`.
 2. Create a nonce using a cryptographic random value generator, such as the [`randomBytes`](https://nodejs.org/api/crypto.html#cryptorandombytessize-callback) function from the `crypto` module.
-3. Store the nonce in the [`locals`](/solid-start/v2/advanced/middleware#locals) object.
+3. Store the nonce in the [`locals`](/solid-start/v2/advanced/middleware#request-scoped-locals) object.
 4. Configure SolidStart to use the nonce in your [`entry-server.tsx`](/solid-start/v2/reference/entrypoints/entry-server) file.
 
 ```tsx tab title="Middleware"