mirrors/PowerShell
0
0
Fork 0
mirror of https://github.com/PowerShell/PowerShell.git synced 2024-11-23 17:53:58 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1885 from pborreli/typos

Browse Source 
Fixed typos
This commit is contained in:
Travis Plunk 2016-08-18 10:38:56 -07:00 committed by GitHub
commit 6fd9a1b1ef
5 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/building/osx.md
View File

@ -78,4 +78,4 @@ start a `powershell` session, and use `Start-PSBuild` from the module.
The output directory will be slightly different because your runtime identifier is different.
PowerShell will be at `./src/powershell-unix/bin/Linux/netcoreapp1.0/osx.10.11-x64/powershell`,
or `osx.10.10` depending on your operating system version.
Note that configration is still `Linux` because it would be silly to make yet another separate configuration when it's used soley to work-around a CLI issue.
Note that configuration is still `Linux` because it would be silly to make yet another separate configuration when it's used soley to work-around a CLI issue.

2
docs/debugging/README.md
View File

@ -104,7 +104,7 @@ The script is self-documented and contains a link to the
corehost
========
The native executable prouduced by .NET CLI will produce trace output
The native executable produced by .NET CLI will produce trace output
if launched with `COREHOST_TRACE=1 ./powershell`.
CoreCLR PAL

4
docs/dev-process/coding-guidelines.md
View File

@ -18,11 +18,11 @@ Here are some general guidelines
* Use of `this` is neither encouraged nor discouraged.
* Avoid more than one blank empty line.
* Public members should use [doc comments](https://msdn.microsoft.com/en-us/library/b2s063f7.aspx),
internal members may use doc comments but it is not enouraged.
internal members may use doc comments but it is not encouraged.
* Public members in a namespace that ends with `Internal`,
for example `System.Management.Automation.Internal` are not considered a supported public API.
Such members are necessarily public as implementation details in code shared between C# and PowerShell script,
or must be available publically by generated code.
or must be available publicly by generated code.
* File encoding should be ASCII (preferred)
or UTF8 (with BOM) if absolutely necessary.

2
docs/dev-process/map-json-files.md
View File

@ -28,7 +28,7 @@ And in PowerShell/PowerShell it mapped into `src/System.Management.Automation/en
Our dev module contains a number of functions to work that can be used to work with this mapping file.
* `Copy-MappedFiles` -- copies files from psl-monad into PowerShell/PowerShell. Used for "sd -> github" integration.
* `Send-GitDiffToSd` -- applies patch from git to **admin** enslistment with respect to all `map.json` files.
* `Send-GitDiffToSd` -- applies patch from git to **admin** enlistment with respect to all `map.json` files.
It supports `-WhatIf` switch.
```

2
docs/dev-process/resx-files.md
View File

@ -31,7 +31,7 @@ A resource file is a simple XML file, and it's easy to edit.
## Convert `.txt` resource files into `.resx` files
`dotnet cli` doesn't support embedding old-fashioned `.txt` resource.
You can do a one-time convertion of `.txt` resources into `.resx` files with a helper function:
You can do a one-time conversion of `.txt` resources into `.resx` files with a helper function:
```
# example, converting all .txt resources under src\Microsoft.WSMan.Management\resources