Updated TOC for docs by removing empty spaces from xml files

Author: VesaJuvonen

docs/spfx/tools-and-libraries.md

@@ -24,6 +24,8 @@ You can choose any one of a number of JavaScript frameworks to develop client-si
 
 Because client-side web parts are components that are dropped into a SharePoint page, we recommend that you choose a JavaScript framework that supports a similar component model. Lightweight frameworks such as React, Handlebars, and Angular 2 all support a component model and are well suited to building client-side web parts. 
 
+We also recommend you to have a look on [SharePoint PnP JavaScript Core library](https://github.com/OfficeDev/PnP-js-core), which is a community driven effort targeted for providing easy access on SharePoint REST APIs. 
+
 ## Node Package Manager (npm)
 
 SharePoint client-side development tools use the [npm](https://www.npmjs.com/) package manager, which is similar to [NuGet](https://www.nuget.org/), to manage dependencies and other required JavaScript helpers. npm is typically included as part of Node.js setup.

docs/spfx/web-parts/guidance/connect-client-side-web-parts-to-aad-secured-resources.md renamed to docs/spfx/web-parts/guidance/call-microsoft-graph-from-your-web-part.md

@@ -1,6 +1,6 @@
 # Use existing JavaScript libraries in SharePoint Framework client-side web parts
 
-When building client-side web parts on the SharePoint Framework you can benefit of existing JavaScript libraries to build powerful solutions. There are however some considerations that you should take into account to ensure that your web parts won't negatively impact the performance of SharePoint pages that they are being used on.
+When building client-side web parts on the SharePoint Framework you can benefit from using existing JavaScript libraries to build powerful solutions. There are however some considerations that you should take into account to ensure that your web parts won't negatively impact the performance of SharePoint pages that they are being used on.
 
 ## Reference existing libraries as packages
 

docs/spfx/web-parts/guidance/use-existing-javascript-libraries.md

@@ -25,9 +25,9 @@
 				<Item text="Known issues" url="spfx/web-parts/basics/known-issues" SEODescription="Known issues with web parts in the SharePoint Framework" />
 			</Item>
 			<Item text="Guidance" url="spfx/web-parts/guidance" SEODescription="">
-				<Item text="Use existing JavaScript libraries in SharePoint Framework client-side web parts" url="spfx/web-parts/guidance/use-existing-javascript-libraries" SEODescription="Use external JavaScript libraries in your client-side web parts." />
-				<Item text="Build SharePoint Framework client-side web parts with Angular v1.x" url="spfx/web-parts/guidance/build-client-side-web-parts-with-angular-1-x" SEODescription="Use Angular 1.x in your SharePoint Framework client-side web parts." />
-				<Item text="Call the Microsoft Graph API using OAuth from your web part" url="spfx/web-parts/guidance/connect-client-side-web-parts-to-aad-secured-resources" SEODescription="Connect your SharePoint Framework client-side web parts to Microsoft Graph API." />
+				<Item text="Use existing JavaScript libraries" url="spfx/web-parts/guidance/use-existing-javascript-libraries" SEODescription="Best practices for using existing JavaScript libraries in your SharePoint client-side web parts." />
+				<Item text="Build web parts with Angular v1.x" url="spfx/web-parts/guidance/build-client-side-web-parts-with-angular-1-x" SEODescription="Use Angular 1.x to build a simple SharePoint Framework client-side web part." />
+				<Item text="Call the Microsoft Graph API" url="spfx/web-parts/guidance/call-microsoft-graph-from-your-web-part" SEODescription="Call the Microsoft Graph API from your SharePoint Framework client-side web part using OAuth." />
 			</Item>
 		</Item>
 	</Item>