(maint) formatting

chocolatey · Apr 19, 2017 · 1ba231a · 1ba231a
1 parent a405260
commit 1ba231a
Show file tree

Hide file tree

Showing 2 changed files with 24 additions and 24 deletions.
diff --git a/AppVeyor/AppVeyorDeploy.ps1 b/AppVeyor/AppVeyorDeploy.ps1
@@ -1,11 +1,11 @@
-#---------------------------------# 
-# Header                          # 
-#---------------------------------# 
+#---------------------------------#
+# Header                          #
+#---------------------------------#
 Write-Host 'Running AppVeyor deploy script' -ForegroundColor Yellow
 
-#---------------------------------# 
-# Update module manifest          # 
-#---------------------------------# 
+#---------------------------------#
+# Update module manifest          #
+#---------------------------------#
 Write-Host 'Creating new module manifest'
 
 $ModuleManifestPath = Join-Path -path "$pwd" -ChildPath ("$env:ModuleName"+'.psd1')
@@ -14,9 +14,9 @@ $ModuleManifest     = Get-Content $ModuleManifestPath -Raw
 Write-Host "Updating module manifest to version: $env:APPVEYOR_BUILD_VERSION"
 [regex]::replace($ModuleManifest,'(ModuleVersion = )(.*)',"`$1'$env:APPVEYOR_BUILD_VERSION'") | Out-File -LiteralPath $ModuleManifestPath
 
-#---------------------------------# 
-# Publish to PS Gallery           # 
-#---------------------------------# 
+#---------------------------------#
+# Publish to PS Gallery           #
+#---------------------------------#
 
 if ( ($env:APPVEYOR_REPO_NAME -notmatch 'chocolatey') -or ($env:APPVEYOR_REPO_BRANCH -notmatch 'master') )
 {

diff --git a/readme.md b/readme.md
@@ -10,7 +10,7 @@ Community Chocolatey DSC Resource
 
 This resource is aimed at getting and installing packages from the choco gallery.
 
-The resource takes the name of the package and will then install that package. 
+The resource takes the name of the package and will then install that package.
 
 See [ExampleConfig.ps1](ExampleConfig.ps1) for example usage.
 
@@ -19,23 +19,23 @@ See list of packages here: https://chocolatey.org/packages
 Contributing
 =============================
 
-Happy to accept new features and fixes. Outstanding issues which can be worked on tagged HelpedWanted under issues. 
+Happy to accept new features and fixes. Outstanding issues which can be worked on tagged HelpedWanted under issues.
 
 Submitting a PR
 =============================
 
-Here's the general process of fixing an issue in the DSC Resource Kit:  
-1. Fork the repository.  
-3. Clone your fork to your machine.  
-4. It's preferred to create a non-master working branch where you store updates.  
-5. Make changes.  
-6. Write pester tests to ensure that the issue is fixed.  
-7. Submit a pull request to the development branch.  
-8. Make sure all tests are passing in AppVeyor for your pull request.  
-9. Make sure your code does not contain merge conflicts.  
-10. Address comments (if any). 
-
-Build and Publishing 
+Here's the general process of fixing an issue in the DSC Resource Kit:
+1. Fork the repository.
+3. Clone your fork to your machine.
+4. It's preferred to create a non-master working branch where you store updates.
+5. Make changes.
+6. Write pester tests to ensure that the issue is fixed.
+7. Submit a pull request to the development branch.
+8. Make sure all tests are passing in AppVeyor for your pull request.
+9. Make sure your code does not contain merge conflicts.
+10. Address comments (if any).
+
+Build and Publishing
 ============================
 
 AppVeyor is used to package up the resource and publish to the Powershell Gallery (on successful build from master branch only). 
@@ -45,4 +45,4 @@ The AppVeyor scripts do the following:
 - Verify best practises using 'PSScriptAnalyzer'
 - Update the version in the manifest file
 - Publish the module to the powershell gallery
-- Checkin updated manifest file to github
+- Checkin updated manifest file to github