Formatting changes

Author: VesaJuvonen

docs/spfx/web-parts/guidance/intercepting-query-changes-in-webparts.md

@@ -9,9 +9,9 @@ localization_priority: Normal
 
 # Intercepting Query String Changes in Web Parts
 
-When building a web part that needs to take into account query string changes you can use the web API `window.___location.search` to read the query string. However if the user proceeds to click a link on the page that contains the same path as the current URL and only the query string changes, the URL in the address bar will be updated but the page will not re-render (due to performance reasons). This document is aimed at showing how you can take advantage of other web APIs to track query string changes and respond to them in your web part.
+When building a web part that needs to take into account query string changes, you can use the web API `window.___location.search` to read the query string. However if the user proceeds to click a link on the page that contains the same path as the current URL and only the query string changes, the URL in the address bar will be updated but the page will not re-render (due to performance reasons). This document is aimed at showing how you can take advantage of other web APIs to track query string changes and respond to them in your web part.
 
-First let's assume you have a basic webpart class that renders the current query string.
+First let's assume you have a basic web part class that renders the current query string.
 
 ```typescript
 export default class HelloWorldWebPart extends BaseClientSideWebPart<IHelloWorldWebPartProps> {
@@ -54,6 +54,6 @@ export default class HelloWorldWebPart extends BaseClientSideWebPart<IHelloWorld
 ```
 
 There are two parts to what we are doing in onInit:
-1. Ensuring that whenever ___pushState is called by other javascript we trigger our `_onUrlChange` method.
-2. Ensuring that whenever the browser fires a 'popstate' event (e.g. user pressing the browser back button) we trigger our `_onUrlChange` method.
 
+1. Ensuring that whenever ___pushState is called by other javascript we trigger our `_onUrlChange` method.
+1. Ensuring that whenever the browser fires a 'popstate' event (for example, user pressing the browser back button) we trigger our `_onUrlChange` method.

docs/toc.yml

@@ -141,7 +141,7 @@
       href: spfx/hyperlinking.md
     - name: Building Office add-ins
       href: spfx/office-addins-create.md
-    - name: Intercepting query string changes in web parts
+    - name: Intercepting query string changes
       href: spfx/web-parts/guidance/intercepting-query-changes-in-webparts.md
   - name: External libraries
     items: