Fix TOC.

README.md

@@ -55,10 +55,10 @@ projects that use wouter: **[Ultra](https://ultrajs.dev/)**,
   - [The list of methods available](#the-list-of-methods-available)
 - [Hooks API](#hooks-api)
   - [`useRoute`: route matching and parameters](#useroute-route-matching-and-parameters)
-  - [`useLocation` hook: working with the history](#uselocation-working-with-the-history)
+  - [`useLocation`: working with the history](#uselocation-working-with-the-history)
     - [Additional navigation parameters](#additional-navigation-parameters)
     - [Customizing the location hook](#customizing-the-location-hook)
-  - [`useParams`: extract matched parameters](#useparams-extract-matched-parameters)
+  - [`useParams`: extracting matched parameters](#useparams-extracting-matched-parameters)
   - [`useRouter`: accessing the router object](#userouter-accessing-the-router-object)
 - [Component API](#component-api)
   - [`<Route path={pattern} />`](#route-pathpattern-)
@@ -283,7 +283,7 @@ Because these hooks have return values similar to `useState`, it is easy and fun
 
 ### `useParams`: extracting matched parameters
 
-This hook allows you to access the parameters exposed through [matching dynamic segments](#matching-dynamic-segments). Internally, we simply wrap your components with a context provider allowing you to access this data anywhere within the `Route` component.
+This hook allows you to access the parameters exposed through [matching dynamic segments](#matching-dynamic-segments). Internally, we simply wrap your components in a context provider allowing you to access this data anywhere within the `Route` component.
 
 This allows you to avoid "prop drilling" when dealing with deeply nested components within the route. **Note:** `useParams` will only extract parameters from the closest parent route.