diff --git a/samples/angular-search/.vscode/settings.json b/samples/angular-search/.vscode/settings.json
index ab46aaa4f..e948448d9 100644
--- a/samples/angular-search/.vscode/settings.json
+++ b/samples/angular-search/.vscode/settings.json
@@ -18,4 +18,6 @@
     "lib": true,
     "temp": true
   }
+,
+"typescript.check.workspaceVersion": false
 }
diff --git a/samples/angular-search/README.md b/samples/angular-search/README.md
index 0935b4f96..18fda9bc1 100644
--- a/samples/angular-search/README.md
+++ b/samples/angular-search/README.md
@@ -10,12 +10,9 @@ available through SharePoint's REST API.
 
 The logic for querying the SharePoint Content Types in the properties of the webpart was in part due to Chris O'Brien and this [blog post](http://www.sharepointnutsandbolts.com/2016/09/sharepoint-framework-spfx-web-part-properties-dynamic-dropdown.html?m=0)
 
-> Note: In order to use the ngOfficeFabric code I use the ModuleLoader to load newer source files than the currently
-> Office Fabric UI in SharePoint Online, which will cause many of the icons not to load properly on the SharePoint
-> Page this webpart is added to.
+> Note: In order to use the ngOfficeFabric code I use the ModuleLoader to load newer source files than the currently Office Fabric UI in SharePoint Online, which will cause many of the icons not to load properly on the SharePoint Page this webpart is added to.
 
-> Note: For the display template of the search results I'm currently using the Office Fabric UI List template. Ideally
-> I was hoping to use the DocumentCard Component, however, that is not yet available through the ngOfficUIFabric.
+> Note: For the display template of the search results I'm currently using the Office Fabric UI List template. Ideally I was hoping to use the DocumentCard Component, however, that is not yet available through the ngOfficUIFabric.
 
 ## Applies to