Minor changes

Author: tomasmu

ChangeLog.md

@@ -2,4 +2,4 @@
 All notable changes will be documented in this file
 
 ## [1.0.0] 2016-10-21
-### Version 1.0.0 released
+### Version 1.0.0 released

README.md

@@ -1,41 +1,38 @@
 # Get NuGet Package Metadata
 Ever wanted to get metadata from your NuGet packages, such as author or license information? 
 Got lost looking for it in Visual Studio? Are you looking for a simple script that is able to 
-output all metadata information from a single command? This cmdlet is easy to use and
-simple to integrate with your build / continuous integration process. If you don't have any
-previous experience with scripting or PowerShell, follow the examples below.
+output all metadata information from a single command?
+Look no further!
+
+This cmdlet is easy to use and simple to integrate with your build / continuous integration process.
+
+If you don't have any previous experience with scripting or PowerShell, follow the examples below.
 
 ## Installation
 
 ## Examples
 ### Simple usage
-By default, the cmdlet recursively searches for .nupkg files relative to the folder you're in.
-If you're using visual studio, open a PowerShell prompt on your project directory and run:
+By default, the cmdlet recursively searches for .nupkg files in the folder you're in.
+Open a PowerShell prompt in your project directory and run:
 ```sh
 $ Get-NuGetMetadata
 ```
 It should output the metadata contents of every NuGet package within the project.
 ## Exporting output
+With powershell it's easy to save the data to file.
 ### To CSV
-With powershell, saving information is as simple as piping the output of the GetNugetMetadata command
-to a different command, which writes data to file.
 ```sh
 $ Get-NuGetMetadata | Export-Csv -NoTypeInformation ./my-metadata-file.csv
 ```
 This produces a file named my-metadata-file.csv in the directory you are in.
 ### To JSON
 Since the Get-NugetMetadata cmdlet produces xml, it can't be easily converted to Json using ConvertTo-Json.
-One workaround is to construct a custom PSObject by filtering properties of the metadata as such:
+One workaround is to pipe via select, which then creates a PSObject that can be converted:
 ```sh
 $ Get-NuGetMetadata | Select-Object id, version, licenseUrl | ConvertTo-Json | Out-File ./my-metadata-file.csv
 ```
 
 
-### Converting output to JSON
-
-
-
-
 ## Release History
 
 * 1.0.0
@@ -44,5 +41,3 @@ $ Get-NuGetMetadata | Select-Object id, version, licenseUrl | ConvertTo-Json | O
 ## License
 
 Distributed under the MIT license. See ``LICENSE`` for more information.
-
-