Updated doc content.

Content updates have been deliverd by the 'content Gods', here they are.

Docs/Askpass.md

@@ -4,7 +4,7 @@
 
 # Usage
 
- Generally speaking, Git will use Git Askpass for Windows and you will only need to interact with any authentication dialogs asking for credentials. As much as possible, Askpass attempts to stay out of sight and out of mind. We believe that Askpass is doing its best job when you forget you're depending on it at all.
+ After installation and configuration, Git will use the Git Askpass and you will only need to interact with any authentication dialogs asking for credentials. The Askpass stays invisible as much as possible, so ideally you’ll forget that you’re depending on Askpass at all.
 
      git askpass
 

Docs/Configuration.md

@@ -1,6 +1,6 @@
 # Configuration Options
 
- For the majority of users, the default configuration is the correct configuration. There will always be those who need special features or the ability to tweak how a service operates.
+ GCM/Askpass work out of the box for most users. Configuration options are available to customize or tweak behavior(s).
  
  The Git Credential Manager for Windows [GCM] can be configured using Git's configuration files, and follows all of the same rules Git does when consuming the files. Global configuration settings override system configuration settings, and local configuration settings override global settings; and because the configuration details exist within Git's configuration files you can use Git's `git config` utility to set, unset, and alter the setting values.
  

Docs/CredentialManager.md

@@ -4,7 +4,7 @@
 
 # Usage
 
- Generally speaking, Git will use the Git Credential Manager for Windows and you will only need to interact with any authentication dialogs asking for credentials. As much as possible, the GCM attempts to stay out of sight and out of mind. We believe that the GCM is doing its best job when you forget you're depending on it at all.
+ After installation, Git will use the Git Credential Manager for Windows and you will only need to interact with any authentication dialogs asking for credentials. The GCM stays invisible as much as possible, so ideally you’ll forget that you’re depending on GCM at all.
 
  Assuming the GCM has been installed, using your favorite Windows console (Command Prompt, PowerShell, ConEmu, etc), use the following command to interact directly with the GCM.
 
@@ -16,7 +16,6 @@
 
  Removes stored credentials for a given URL. Any future attempts to authenticate with the remote will require authentication steps to be completed again.
 
-
 ### deploy _[--path \<installion_path\>] [--passive] [--force]_
 
  Deploys the Git Credential Manager for Windows package and sets Git configuration to use the helper.

Docs/Development.md

@@ -1,6 +1,6 @@
 # Development and Debugging
 
- Development on the GCM geenrally requires Visual Studio 2015 or newer. Luckily, Visual Studio offers a free [Community Edition](https://www.visualstudio.com/products/visual-studio-community-vs), for those of us who do not have an enterpise copy installed.
+ Developing for GCM and/or Askpass requires Visual Studio 2015 or newer, any version (including the free [Community Edition](https://www.visualstudio.com/products/visual-studio-community-vs)).
 
 ## Getting Started
 

Docs/Faq.md

@@ -1,6 +1,6 @@
 # FAQ
 
- Frequently asked questions collected from our [issues page](https://github.com/Microsoft/Git-Credential-Manager-for-Windows/issues), our [Twitter feed](https://twitter.com/microsoftgit), and other sources. Please look through this list of questions-and-answers before posting a new issue on a topic.
+ If you have an issue using GCM or Askpass, please review the following FAQ and check our [issue history](https://github.com/Microsoft/Git-Credential-Manager-for-Windows/issues) or our [Twitter feed](https://twitter.com/microsoftgit) before opening up an item on our issues page on Github.
 
 ## Q: Why am always prompted for my username and password?