Changed the paths in several config sections in the getting started guide to match the install paths in the earlier parts of the guide.

Author: csc027

docs/guide/getting_started.md

@@ -74,16 +74,22 @@ local on_attach = function(client, bufnr)
 	vim.keymap.set('n', '<Leader>td', vim.lsp.buf.type_definition, bufopts)
 end
 
-local bundle_path = '<Path to where PowerShell Editor Services was installed>'
+local home_directory = os.getenv('HOME')
+if home_directory == nil then
+    home_directory = os.getenv('USERPROFILE')
+end
+
+-- The bundle_path is where PowerShell Editor Services was installed
+local bundle_path = home_directory .. '/Desktop/PowerShellEditorServices'
 
 require('lspconfig')['powershell_es'].setup {
 	bundle_path = bundle_path,
 	on_attach = on_attach
 }
 ```
 
-> NOTE: Be sure to set the bundle_path variable, otherwise the server will not
-> know the path to start the server.
+> 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.
 
 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
@@ -99,9 +105,10 @@ require('lspconfig')['powershell_es'].setup {
 As another example, you can set the bundled PSScriptAnalyzer's custom rule path
 like so:
 ```lua
+local custom_settings_path = home_directory .. '/PSScriptAnalyzerSettings.psd1'
 require('lspconfig')['powershell_es'].setup {
 	bundle_path = bundle_path,
 	on_attach = on_attach,
-	settings = { powershell = { scriptAnalysis = { settingsPath = os.getenv('HOME') .. 'PSScriptAnalyzerSettings.psd1' } } }
+	settings = { powershell = { scriptAnalysis = { settingsPath = custom_settings_path } } }
 }
 ```