Minor Grammatical Updates (SharePoint#713)

Also, fixed the tutorial link

Author: thechriskent

docs/spfx/web-parts/basics/working-with-requestdigest.md

@@ -1,28 +1,28 @@
 # Working with the original __RequestDigest
 
-There is a lot of code written to work with the classic SharePoint pages that you can use with the SharePoint Framework, but sometimes certain components or variables aren't there. One example is the __REQUESTDIGEST form field.  In an ideal world, you wouldn't use a global variable to access the digest, you'd just use the updated **HttpRequest** object to make your SharePoint call, and it will handle all the digest / auth logic for you (including things like expired tokens).  The [Connect your client-side web part to SharePoint (Hello world part 2)](https://github.com/SharePoint/sp-dev-docs/wiki/HelloWorld,-Talking-to-SharePoint) article shows you how to do this.
+There is a lot of code written to work with classic SharePoint pages that you can use with the SharePoint Framework, but sometimes certain components or variables aren't there. One example is the `__REQUESTDIGEST` form field. In an ideal world, you wouldn't use a global variable to access the digest, you'd just use the updated `HttpRequest` object to make your SharePoint call, and it will handle all the digest/auth logic for you (including things like expired tokens). The [Connect your client-side web part to SharePoint (Hello world part 2)](https://dev.office.com/sharepoint/docs/spfx/web-parts/get-started/connect-to-sharepoint) article demonstrates how to do this.
 
-However, if your existing code uses some older constructs, through the power of client side code and DOM manipulation, it's fairly easy to add these back to a page.  The key is to hook into the **onInit** method in the base web part class, and pull the create the DOM element that you expect to be there.  Here's an example that creates the __REQESTDIGEST form element.
+However, if your existing code uses some older constructs, through the power of client-side code and DOM manipulation, it's fairly easy to add these back to a page. The key is to hook into the `onInit` method in the base web part class and create the DOM element that you expect to be there. Here's an example that creates the `__REQUESTDIGEST` form element:
 
 ```JavaScript
     public onInit<T>(): Promise<T>
     {
     // does the digest exist?
     if ( !document.getElementById('__REQUESTDIGEST') )
     {
-      // OK, the request digest does not exist.  Let's create it.
+      // OK, the request digest does not exist. Let's create it.
       // first, grab the digest value out of the contextWebInfo object (if it exists).
       var digestValue: string;
       try{
         digestValue = (window as any)._spClientSidePageContext.contextWebInfo.FormDigestValue;
       }
       catch (exception){
-        // there is no digest on this page, so just return.  This can easily happen on the local workbench
+        // there is no digest on this page, so just return. This can easily happen on the local workbench
         return Promise.resolve();
       }
 
       if (digestValue){
-        // OK, now lets create the digest input form.  It looks like this -
+        // OK, now lets create the digest input form. It looks like this:
         // <input type="hidden" name="__REQUESTDIGEST" id="__REQUESTDIGEST" value="blahblahblahblahblahblah, July23 -0000 or something like that">
         const requestDigestInput: Element = document.createElement('input');
         requestDigestInput.setAttribute('type', 'hidden');
@@ -40,12 +40,12 @@ However, if your existing code uses some older constructs, through the power of
     }
 ```
 
->**Note:** There is a better way to get the current digest value that will handle all of the caching / expiring / refetching / etc.  Give this a try.  You'll need to import digestCacheServiceKey and IDigestCache from sp-client-base
+>**Note:** There is a better way to get the current digest value that will handle all of the caching, expiring, refetching, etc. Give this a try (You'll need to import `digestCacheServiceKey` and `IDigestCache` from **sp-client-base**):
 
 ```JavaScript
     var digestCache:IDigestCache = this.context.serviceScope.consume(digestCacheServiceKey);
     digestCache.fetchDigest(this.context.pageContext.web.serverRelativeUrl).then((digest: string) => {
       // Do Something with the digest
       console.log(digest);
     });
-```
+```