Improve step 4 of "Create .. PowerShell module.."

Improve instructions in step 4 of "Create and populate the PowerShell module and module manifest"
# "Take following" should be "The following"
# Step 4 should also explicitly instruct the reader to export the Get-Hello Function she created in step 1.

Author: charliearcuri

docs/artifacts/tutorials/private-powershell-library.md

@@ -118,7 +118,9 @@ Create a folder named `Get-Hello`. Within that folder create a `Get-Hello.psm1`
     RootModule = 'Get-Hello.psm1'
     ```
 
-4. The `FunctionsToExport = @()` section is meant to define the module's exported functions. This is simply a list of all exported functions. Take following is an example from `PowerShellGet.psd1`:
+4. The `FunctionsToExport = @()` section is meant to define the module's exported functions. This is simply a list of all exported functions. The following is an example from `PowerShellGet.psd1`:
+
+
 
     ```powershell
     FunctionsToExport = @('Install-Module',
@@ -148,6 +150,9 @@ Create a folder named `Get-Hello`. Within that folder create a `Get-Hello.psm1`
                           'Update-ModuleManifest')
     ```
     
+    > [!TIP]
+    > your module manifest should export the `Get-Hello` function you created in Step 1 
+    
 5. It is also possible to define a list of files as part of your module. Just add this list under `FileList=@()`.
 
     ```powershell
@@ -288,4 +293,4 @@ We now have our private PowerShell repository to publish and download our packag
 
 ## Credit
 
-Credit to this [article on Medium](https://medium.com/@jsrice7391/using-vsts-for-your-companys-private-powershell-library-e333b15d58c8) that was used as a source for this tutorial.
+Credit to this [article on Medium](https://medium.com/@jsrice7391/using-vsts-for-your-companys-private-powershell-library-e333b15d58c8) that was used as a source for this tutorial.