diff --git a/docs/spfx/web-parts/guidance/intercepting-query-changes-in-webparts.md b/docs/spfx/web-parts/guidance/intercepting-query-changes-in-webparts.md
index 2a81786c72..c0d9ef2bfc 100644
--- a/docs/spfx/web-parts/guidance/intercepting-query-changes-in-webparts.md
+++ b/docs/spfx/web-parts/guidance/intercepting-query-changes-in-webparts.md
@@ -2,7 +2,7 @@
 title: Intercepting Query String Changes in Web Parts
 description: Building web parts that respond to query string changes.
 ms.author: bekaise
-ms.date: 01/28/2020
+ms.date: 04/22/2020
 ms.prod: sharepoint
 localization_priority: Normal
 ---
@@ -16,7 +16,7 @@ First let's assume you have a basic web part class that renders the current quer
 ```typescript
 export default class HelloWorldWebPart extends BaseClientSideWebPart<IHelloWorldWebPartProps> {
   public render(): void {
-    this.domElement.innerHTML = window.location.query;
+    this.domElement.innerHTML = window.location.search;
   }
 }
 ```
@@ -26,28 +26,30 @@ We can use the following changes to trigger our web part to re-render in the eve
 ```typescript
 export default class HelloWorldWebPart extends BaseClientSideWebPart<IHelloWorldWebPartProps> {
   public onInit(): Promise<void> {
-    (function (history) {
+    ((history) => {
       var pushState = history.pushState;
-      history.pushState = function (state, key, path) {
-          this._onUrlChange();
-          return pushState.apply(history, arguments);
+      history.pushState = (state, key, path) => {          
+          pushState.apply(history, [state, key, path]);
+          this._onUrlChange(path);
       };
     })(window.history);
 
     window.addEventListener('popstate', function (e) {
-      this._onUrlChange();
+      //Currently browsing by the browser history buttons ( back / forward ) doesnt cause any effect on a sp conditionally loaded page.
+      //this._onUrlChange();
     });
 
     return Promise.resolve();
   }
 
   public render(): void {
-    this.domElement.innerHTML = window.location.query;
+    this.domElement.innerHTML = window.location.search;
   }
 
-  private _onUrlChange(): void {
+  private _onUrlChange(newpath = window.location.search): void {    
     // any logic you might want to trigger when the query string updates
     // e.g. fetching data
+    // e.g. logging the URL changes // console.log(newpath)
     this.render();
   }
 }
@@ -56,4 +58,4 @@ 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.
-1. Ensuring that whenever the browser fires a 'popstate' event (for example, user pressing the browser back button) we trigger our `_onUrlChange` method.
\ No newline at end of file
+1. Ensuring that whenever the browser fires a 'popstate' event (for example, user pressing the browser back button) we trigger our `_onUrlChange` method.