Changed licensing to BSD 3-Clause

Fixed some spelling errors in README.
Added additional usage information

Author: bitform

Encrypt-Script.ps1

@@ -5,7 +5,7 @@ function Encrypt-Script {
 
  PowerSploit Module - Encrypt-Script
  Author: Matthew Graeber (@mattifestation)
- License: GNU GPL v2
+ License: BSD 3-Clause
  
 .Description
 

Get-GPPPassword.ps1

@@ -5,7 +5,7 @@ function Get-GPPPassword {
 
  Get-GPPPassword retrieves the plaintext password for accounts pushed through Group Policy in groups.xml.
  Author: Chris Campbell (@obscuresec)
- License: GNU GPL v2
+ License: BSD 3-Clause
  
 .Description
 

Inject-Dll.ps1

@@ -5,7 +5,7 @@ function Inject-Dll {
 
  PowerSploit Module - Inject-Dll
  Author: Matthew Graeber (@mattifestation)
- License: GNU GPL v2
+ License: BSD 3-Clause
  
 .Description
 

Inject-Shellcode.ps1

@@ -5,7 +5,7 @@ function Inject-Shellcode {
 
  PowerSploit Module - Inject-Shellcode
  Author: Matthew Graeber (@mattifestation)
- License: GNU GPL v2
+ License: BSD 3-Clause
  
 .Description
 

Invoke-ReverseDnsLookup.ps1

@@ -6,7 +6,7 @@ function Invoke-ReverseDnsLookup
 
  PowerSploit Module - Invoke-ReverseDnsLookup
  Author: Matthew Graeber (@mattifestation)
- License: GNU GPL v2
+ License: BSD 3-Clause
  
 .Description
 

LICENSE

@@ -0,0 +1,16 @@
+PowerSploit is provided under the 3-clause BSD license below.
+
+*************************************************************
+
+Copyright (c) 2012, Matthew Graeber
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
+
+    Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
+    Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
+    The names of its contributors may not be used to endorse or promote products derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+

PE_Tools/Get-DllLoadPath.ps1

@@ -4,7 +4,7 @@ function Get-DllLoadPath {
 
  PowerSploit Module - Get-DllLoadPath
  Author: Matthew Graeber (@mattifestation)
- License: GNU GPL v2
+ License: BSD 3-Clause
  
 .Description
 

PE_Tools/Get-PEArchitecture.ps1

@@ -4,7 +4,7 @@ function Get-PEArchitecture {
 
  PowerSploit Module - Get-PEArchitecture
  Author: Matthew Graeber (@mattifestation)
- License: GNU GPL v2
+ License: BSD 3-Clause
  
 .Description
 

README

@@ -24,34 +24,42 @@ Get-GPPPassword:
 
 Invoke-ReverseDnsLookup:
 
-   Invoke-ReverseDnsLookup scans an IP address range for DNS PTR records. This script is useful for performing DNS reconnaisance prior to conducting an authorized penetration test.
+   Invoke-ReverseDnsLookup scans an IP address range for DNS PTR records. This script is useful for performing DNS reconnaissance prior to conducting an authorized penetration test.
 
 ----------
 .\PE_Tools
 ----------
 
 An assortment of scripts used to parse/manipulate Windows portable executables
 
+-------
+License
+-------
+
+The PowerSploit project and all individual scripts are under the BSD 3-Clause license.
+
 -----
 Usage
 -----
 
-   Refer to the comment-based help in each individual script for usage information.
+The scripts in PowerSploit are not scripts in the traditional sense in that you just execute them at the command line and go. Rather, each script defines a function that can consequently be called at the command line. This method, in my opinion, provides more flexibility with PowerShell. If executing these scripts as traditional scripts ("dot source") becomes necessary, you can always append the command you want to execute after the function definition.
+
+Refer to the comment-based help in each individual script for detailed usage information.
 
 
 ------------------
 Script Style Guide
 ------------------
 
-For all contributers and future contributers to PowerSploit, I ask that you follow this style guide when writing your scripts.
+For all contributors and future contributors to PowerSploit, I ask that you follow this style guide when writing your scripts.
 
 * Avoid Write-Host at all costs. You should output custom objects instead. For more information on creating custom objects, read these articles:
    * http://blogs.technet.com/b/heyscriptingguy/archive/2011/05/19/create-custom-objects-in-your-powershell-script.aspx
    * http://technet.microsoft.com/en-us/library/ff730946.aspx
 
 * If you want to display relevant debugging information to the screen, use Write-Verbose. The user can always just tack on '-Verbose'.
 
-* Always provide descriptive, comment-based help for every script. Also, be sure to include your name and a GNU GPL v2 license.
+* Always provide descriptive, comment-based help for every script. Also, be sure to include your name and a BSD 3-Clause license.
 
 * Make sure all functions follow the proper PowerShell verb-noun agreement. Use Get-Verb to list the default verbs used by PowerShell.
 
@@ -76,9 +84,9 @@ For all contributers and future contributers to PowerSploit, I ask that you foll
 
 * Don't use any aliases. They make code more difficult to read for people who are unfamiliar with a particular alias.
 
-* Don't let commands run on for too long. For example, a pipeline is a natural place for a linebreak.
+* Don't let commands run on for too long. For example, a pipeline is a natural place for a line break.
 
-* Don't go overboard with inline comments. Only use them when certian aspects of the code might be confusing to a reader.
+* Don't go overboard with inline comments. Only use them when certain aspects of the code might be confusing to a reader.
 
 * Use Out-Null to suppress unwanted/irrelevant output.