docs: address RSC doc review follow-ups (round 2)

- Add `connect(` to the RSC audit grep checklist so it stays
  consistent with the "What to look for" section (which already lists
  Redux `connect()` as requiring `'use client'`). The `(` suffix
  avoids false positives like `connection`/`connected`.
- Replace the misleading "no require() call emitted" phrasing for
  `resolve.fallback: false` with "imports resolve to nothing; no shim
  bundled" — webpack resolves the import to an empty module rather
  than suppressing the require() entirely.
- Make the `additionalContext` MessageChannel example self-contained
  by showing `module.exports = config;` and linking to the node
  renderer JS configuration reference.

Author: justin808

docs/oss/migrating/rsc-troubleshooting.md

@@ -862,7 +862,7 @@ externals: {
 **Correct approach:**
 
 ```js
-// In serverWebpackConfig.js -- tells webpack to omit these modules (no require() call emitted)
+// In serverWebpackConfig.js -- tells webpack not to polyfill these modules (imports resolve to nothing; no shim bundled)
 resolve: {
   fallback: {
     path: false,
@@ -872,7 +872,7 @@ resolve: {
 }
 ```
 
-`resolve.fallback: false` tells webpack to omit the module at build time — no fallback shim is bundled and no `require()` call is emitted. The RSC bundle does not need this workaround because it runs in full Node.js where `require()` is available and Node builtins work normally.
+`resolve.fallback: false` tells webpack not to provide a polyfill for the module — the import resolves to an empty module at build time and no fallback shim is bundled. The RSC bundle does not need this workaround because it runs in full Node.js where `require()` is available and Node builtins work normally.
 
 ### MessageChannel Not Defined
 
@@ -890,8 +890,12 @@ const config = {
   // ... other options
   additionalContext: { MessageChannel },
 };
+
+module.exports = config; // export from node-renderer.js
 ```
 
+See the [node renderer JS configuration reference](../building-features/node-renderer/js-configuration.md) for where `config` is consumed.
+
 **Fallback:** If you cannot change the renderer config (e.g., a build-only setup without renderer config control), inject a minimal `MessageChannel` polyfill at the top of the server bundle using webpack's `BannerPlugin`. The polyfill only needs to support `port2.postMessage` triggering `port1.onmessage`, which is all React's scheduler requires:
 
 ```js

docs/pro/react-server-components/upgrading-existing-pro-app.md

@@ -71,7 +71,7 @@ There is no warning when a component is auto-classified as a server component. I
 
 Before proceeding to Step 1:
 
-- [ ] Search your component source files for `useState`, `useEffect`, `useLayoutEffect`, `useInsertionEffect`, `useContext`, `useRef`, `useImperativeHandle`, `useReducer`, `useCallback`, `useMemo`, `useTransition`, `useDeferredValue`, `useId`, `useSyncExternalStore`, `useOptimistic`, `useFormStatus`, `useSelector`, `useDispatch`, `useNavigate`, `useLocation`, `useParams`, `ReactOnRails.getStore`, `ReactOnRails.authenticityToken`
+- [ ] Search your component source files for `useState`, `useEffect`, `useLayoutEffect`, `useInsertionEffect`, `useContext`, `useRef`, `useImperativeHandle`, `useReducer`, `useCallback`, `useMemo`, `useTransition`, `useDeferredValue`, `useId`, `useSyncExternalStore`, `useOptimistic`, `useFormStatus`, `useSelector`, `useDispatch`, `connect(`, `useNavigate`, `useLocation`, `useParams`, `ReactOnRails.getStore`, `ReactOnRails.authenticityToken`
 - [ ] Check all `.server.jsx` files -- these almost certainly need `'use client'`
 - [ ] Check components that use `StaticRouter` (SSR wrapper, not a client API — but the file likely uses other client APIs)
 - [ ] Verify no component relies on browser globals (`window`, `document`) without `'use client'`