Merge pull request #2181 from reduxjs/docs/update-context-page

Author: markerikson

docs/using-react-redux/accessing-store.md

@@ -17,7 +17,7 @@ store interaction is handled. In typical usage, your own components should never
 won't ever reference the store directly. React Redux also internally handles the details of how the store and state are
 propagated to connected components, so that this works as expected by default.
 
-However, there may be certain use cases where you may need to customize how the store and state are propagated to
+However, there may be certain use cases where you may need to customize how the store is passed to
 connected components, or access the store directly. Here are some examples of how to do this.
 
 ## Understanding Context Usage
@@ -26,8 +26,7 @@ Internally, React Redux uses [React's "context" feature](https://react.dev/learn
 Redux store accessible to deeply nested connected components. As of React Redux version 6, this is normally handled
 by a single default context object instance generated by `React.createContext()`, called `ReactReduxContext`.
 
-React Redux's `<Provider>` component uses `<ReactReduxContext.Provider>` to put the Redux store and the current store
-state into context, and `connect` uses `useContext(ReactReduxContext)` to read those values and handle updates.
+React Redux's `<Provider>` component uses `<ReactReduxContext.Provider>` to put the Redux store and internal subscription wrappers into context. `useSelector`, `useDispatch`, and `connect` call `useContext(ReactReduxContext)` to read those values and handle updates.
 
 ## Using the `useStore` Hook