Cleaned up some sections in the getting started guide to make ot more readable.

Author: csc027

docs/guide/getting_started.md

@@ -57,7 +57,7 @@ Expand-Archive -Path $ZipPath -DestinationPath $InstallPath;
 
 #### Setup Keybindings and Path Information
 Once the basic language configurations have been installed, add this to your
-init.lua:
+init.lua located in `$XDG_CONFIG_HOME`:
 ```lua
 local on_attach = function(client, bufnr)
 	-- Enable completion triggered by <c-x><c-o>
@@ -93,6 +93,14 @@ require('lspconfig')['powershell_es'].setup {
 > NOTE: Be sure to set the bundle_path variable to the correct location,
 > otherwise the server will not know the path to start the server.
 
+If you use an `init.vim` file, you may put the keybinding and path configuration
+in your `init.vim` with the `lua` heredoc syntax instead.
+```vim
+lua << EOF
+-- lua keybindings and path configuration here
+EOF
+```
+
 #### Configure Additional Settings
 To further configure the server, you can supply settings to the setup table.
 For example, you can set the code formatting preset to one true brace style
@@ -105,8 +113,7 @@ require('lspconfig')['powershell_es'].setup {
 }
 ```
 
-As another example, you can set the bundled PSScriptAnalyzer's custom rule path
-like so:
+You can also set the bundled PSScriptAnalyzer's custom rule path like so:
 ```lua
 local custom_settings_path = home_directory .. '/PSScriptAnalyzerSettings.psd1'
 require('lspconfig')['powershell_es'].setup {