From e22b5de14c85747a160ee511bbd7fe46568d808f Mon Sep 17 00:00:00 2001 From: Bobby Reed Date: Mon, 30 Apr 2018 08:09:13 -0400 Subject: [PATCH 1/2] Batch automation: Formatting fixes --- .../about_Functions_Advanced_Parameters.md | 15 +++-- .../about_Functions_CmdletBindingAttribute.md | 3 +- .../about_Functions_OutputTypeAttribute.md | 9 ++- .../About/about_Group_Policy_Settings.md | 7 +-- .../About/about_Hash_Tables.md | 59 +++++++++---------- .../About/about_History.md | 5 +- .../About/about_If.md | 5 +- .../About/about_Job_Details.md | 43 +++++++------- .../About/about_Jobs.md | 19 +++--- .../About/about_Join.md | 3 +- .../About/about_Language_Modes.md | 7 +-- .../About/about_Line_Editing.md | 5 +- .../About/about_locations.md | 3 +- .../About/about_logical_operators.md | 3 +- 14 files changed, 89 insertions(+), 97 deletions(-) diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md index 845df5ff8a24..21a65d4ae5d3 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md @@ -1,11 +1,10 @@ ---- +--- ms.date: 11/28/2017 schema: 2.0.0 locale: en-us keywords: powershell,cmdlet title: about_Functions_Advanced_Parameters --- - # About Functions Advanced Parameters # SHORT DESCRIPTION @@ -514,7 +513,7 @@ greater than or equal to the current date. Param ( [parameter()] - [ValidateScript({$_ -ge (get-date)})] + [ValidateScript({$_ -ge (Get-Date)})] [DateTime] $EventDate ) @@ -524,7 +523,7 @@ In the following example, the value of the variable $date must be greater than or equal to the current date and time. ```powershell -[DateTime][ValidateScript({$_ -ge (get-date)})]$date = (get-date) +[DateTime][ValidateScript({$_ -ge (Get-Date)})]$date = (Get-Date) ``` ## ValidateSet Attribute @@ -660,19 +659,19 @@ function Get-Sample { { if ($path -match ".HKLM.:") { - $attributes = new-object -Type ` + $attributes = New-Object -Type ` System.Management.Automation.ParameterAttribute $attributes.ParameterSetName = "__AllParameterSets" $attributes.Mandatory = $false - $attributeCollection = new-object ` + $attributeCollection = New-Object ` -Type System.Collections.ObjectModel.Collection[System.Attribute] $attributeCollection.Add($attributes) - $dynParam1 = new-object -Type ` + $dynParam1 = New-Object -Type ` System.Management.Automation.RuntimeDefinedParameter("dp1", [Int32], $attributeCollection) - $paramDictionary = new-object ` + $paramDictionary = New-Object ` -Type System.Management.Automation.RuntimeDefinedParameterDictionary $paramDictionary.Add("dp1", $dynParam1) return $paramDictionary diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_CmdletBindingAttribute.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_CmdletBindingAttribute.md index bd92c36dbcde..0d5ff885c073 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_CmdletBindingAttribute.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_CmdletBindingAttribute.md @@ -1,11 +1,10 @@ ---- +--- ms.date: 11/28/2017 schema: 2.0.0 locale: en-us keywords: powershell,cmdlet title: about_Functions_CmdletBindingAttribute --- - # About Functions CmdletBindingAttribute # SHORT DESCRIPTION diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_OutputTypeAttribute.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_OutputTypeAttribute.md index 0c5b2f4167dc..37fe01117e30 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_OutputTypeAttribute.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_OutputTypeAttribute.md @@ -1,11 +1,10 @@ ---- +--- ms.date: 01/03/2018 schema: 2.0.0 locale: en-us keywords: powershell,cmdlet title: about_Functions_OutputTypeAttribute --- - # About Functions OutputTypeAttribute ## SHORT DESCRIPTION @@ -121,7 +120,7 @@ function Send-Greeting To see the resulting output type property, use the Get-Command cmdlet. ``` -PS C:> (Get-Command Send-Greeting).OutputType +PS> (Get-Command Send-Greeting).OutputType Name Type ---- ---- @@ -178,7 +177,7 @@ function Get-Time The Get-Type method confirms that the function returns a string. ``` -PS C:> (Get-Time -DateTime (Get-Date)).Gettype().FullName +PS> (Get-Time -DateTime (Get-Date)).Gettype().FullName System.String ``` @@ -186,7 +185,7 @@ However, the OutputType property, which gets its value from the OutputType attribute, reports that the function returns a DateTime object. ``` -PS C:> (Get-Command Get-Time).OutputType +PS> (Get-Command Get-Time).OutputType Name Type ---- ---- diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_Group_Policy_Settings.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_Group_Policy_Settings.md index c633b6716af8..0d2920f82884 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_Group_Policy_Settings.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_Group_Policy_Settings.md @@ -1,11 +1,10 @@ ---- +--- ms.date: 11/28/2017 schema: 2.0.0 locale: en-us keywords: powershell,cmdlet title: about_Group_Policy_Settings --- - # About Group Policy Settings # SHORT DESCRIPTION @@ -101,8 +100,8 @@ The module must be imported into the session and the setting is effective only in the current session. ```powershell -PS C:> Import-Module -PS C:> (Get-Module ).LogPipelineExecutionDetails = $true +PS> Import-Module +PS> (Get-Module ).LogPipelineExecutionDetails = $true ``` To turn on module logging for all sessions on a particular computer, diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_Hash_Tables.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_Hash_Tables.md index 816b8aefe372..b1f9775991d6 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_Hash_Tables.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_Hash_Tables.md @@ -1,11 +1,10 @@ ---- +--- ms.date: 11/28/2017 schema: 2.0.0 locale: en-us keywords: powershell,cmdlet title: about_Hash_Tables --- - # About Hash Tables ## SHORT DESCRIPTION @@ -109,7 +108,7 @@ place the ordered attribute before the variable name, the command fails with the following error message. ```powershell -PS C:\> [ordered]$hash = @{} +PS> [ordered]$hash = @{} At line:1 char:1 + [ordered]$hash = @{} + [!INCLUDE[]()] @@ -122,7 +121,7 @@ eption To correct the expression, move the [ordered] attribute. ```powershell -PS C:\> $hash = [ordered]@{} +PS> $hash = [ordered]@{} ``` You can cast an ordered dictionary to a hash table, but you cannot recover the @@ -130,9 +129,9 @@ ordered attribute, even if you clear the variable and enter new values. To re-establish the order, you must remove and recreate the variable. ``` -PS C:\> [hashtable]$hash = [ordered]@{ +PS> [hashtable]$hash = [ordered]@{ >> Number = 1; Shape = "Square"; Color = "Blue"} -PS C:\> $hash +PS> $hash Name Value ---- ----- @@ -148,7 +147,7 @@ By default, a hash tables is displayed as a table with one column for keys and one for values. ```powershell -C:\PS> $hash +PS> $hash Name Value ---- ----- @@ -161,12 +160,12 @@ Hash tables have Keys and Values properties. Use dot notation to display all of the keys or all of the values. ```powershell -C:\PS> $hash.keys +PS> $hash.keys Number Shape Color -C:\PS> $hash.values +PS> $hash.values 1 Square Blue @@ -184,10 +183,10 @@ $hashtable. For example: ```powershell -C:\PS> $hash.Number +PS> $hash.Number 1 -C:\PS> $hash.Color +PS> $hash.Color Blue ``` @@ -203,7 +202,7 @@ Hash tables have a Count property that indicates the number of key-value pairs in the hash table. ```powershell -C:\PS> $hash.count +PS> $hash.count 3 ``` @@ -214,7 +213,7 @@ If the key is a string value, enclose the key name in quotation marks. For example: ```powershell -C:\PS> $hash["Number"] +PS> $hash["Number"] 1 ``` @@ -296,28 +295,28 @@ The following statement creates a hash table of process name strings and process object values and saves it in the \$p variable. ```powershell -$p = @{"PowerShell" = (get-process PowerShell); -"Notepad" = (get-process notepad)} +$p = @{"PowerShell" = (Get-Process PowerShell); +"Notepad" = (Get-Process notepad)} ``` You can display the hash table in \$p and use the key-name properties to display the values. ```powershell -C:\PS> $p +PS> $p Name Value ---- ----- PowerShell System.Diagnostics.Process (PowerShell) Notepad System.Diagnostics.Process (notepad) -C:\PS> $p.PowerShell +PS> $p.PowerShell Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName ------- ------ ----- ----- ----- ------ -- ----------- 441 24 54196 54012 571 5.10 1788 PowerShell -C:\PS> $p.keys | foreach {$p.$_.handles} +PS> $p.keys | ForEach-Object {$p.$_.handles} 441 251 ``` @@ -328,14 +327,14 @@ Service object that represents the WinRM service, and the value is the current status of the service. ```powershell -C:\PS> $p = $p + @{(Get-Service WinRM) = ((Get-Service WinRM).Status)} +PS> $p = $p + @{(Get-Service WinRM) = ((Get-Service WinRM).Status)} ``` You can display and access the new key/value pair by using the same methods that you use for other pairs in the hash table. ```powershell -C:\PS> $p +PS> $p Name Value ---- ----- @@ -343,7 +342,7 @@ PowerShell System.Diagnostics.Process (PowerShell) Notepad System.Diagnostics.Process (notepad) System.ServiceProcess.Servi... Running -C:\PS> $p.keys +PS> $p.keys PowerShell Notepad @@ -351,7 +350,7 @@ Status Name DisplayName ------ ---- ----------- Running winrm Windows Remote Management (WS-Manag... -C:\PS> $p.keys | foreach {$_.name} +PS> $p.keys | ForEach-Object {$_.name} winrm ``` @@ -361,13 +360,13 @@ in which the key is a string, Hash2, and the value is a hash table with three key/value pairs. ```powershell -C:\PS> $p = $p + @{"Hash2"= @{a=1; b=2; c=3}} +PS> $p = $p + @{"Hash2"= @{a=1; b=2; c=3}} ``` You can display and access the new values by using the same methods. ```powershell -C:\PS> $p +PS> $p Name Value ---- ----- @@ -376,7 +375,7 @@ Notepad System.Diagnostics.Process (notepad) System.ServiceProcess.Servi... Running Hash2 {a, b, c} -C:\PS> $p.Hash2 +PS> $p.Hash2 Name Value ---- ----- @@ -384,7 +383,7 @@ a 1 b 2 c 3 -C:\PS> $p.Hash2.b +PS> $p.Hash2.b 2 ``` @@ -401,7 +400,7 @@ For example, the following commands enumerate the keys and values in the hash table in the \$p variable and then sort the keys in alphabetical order. ```powershell -C:\PS> $p.GetEnumerator() | Sort-Object -Property key +PS> $p.GetEnumerator() | Sort-Object -Property key Name Value ---- ----- @@ -414,7 +413,7 @@ The following command uses the same procedure to sort the hash values in descending order. ```powershell -C:\PS> $p.getenumerator() | Sort-Object -Property Value -Descending +PS> $p.getenumerator() | Sort-Object -Property Value -Descending Name Value ---- ----- @@ -463,7 +462,7 @@ The following command creates a here-string of the key/value pairs and then saves it in the \$string variable. ```powershell -C:\PS> $string = @" +PS> $string = @" Msg1 = Type "Windows". Msg2 = She said, "Hello, World." Msg3 = Enter an alias (or "nickname"). @@ -474,7 +473,7 @@ This command uses the ConvertFrom-StringData cmdlet to convert the here-string into a hash table. ```powershell -C:\PS> ConvertFrom-StringData $string +PS> ConvertFrom-StringData $string Name Value ---- ----- diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_History.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_History.md index eca45af0808f..7ffe365673d7 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_History.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_History.md @@ -1,11 +1,10 @@ ---- +--- ms.date: 06/09/2017 schema: 2.0.0 locale: en-us keywords: powershell,cmdlet title: about_History --- - # About History ## Short Description @@ -88,5 +87,5 @@ are completed only when you exit the prompt level.) - [about_Line_Editing](about_Line_Editing.md) - [about_Preference_Variables](about_Preference_Variables.md) -- [about_Profiles](about_Profiles.md) +- [about_Profiles](http://go.microsoft.com/fwlink/?LinkID=113729) - [about_Variables](about_Variables.md) \ No newline at end of file diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_If.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_If.md index 09c512a0672c..bcd90c6b3698 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_If.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_If.md @@ -1,18 +1,19 @@ ---- +--- ms.date: 06/09/2017 schema: 2.0.0 locale: en-us keywords: powershell,cmdlet title: about_If --- - # About If ## SHORT DESCRIPTION + Describes a language command you can use to run statement lists based on the results of one or more conditional tests. ## LONG DESCRIPTION + You can use the If statement to run code blocks if a specified conditional test evaluates to true. You can also specify one or more additional conditional tests to run if all the prior tests evaluate to false. Finally, diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_Job_Details.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_Job_Details.md index 1eaf4b1779ec..7f3def34c33a 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_Job_Details.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_Job_Details.md @@ -1,11 +1,10 @@ ---- +--- ms.date: 11/28/2017 schema: 2.0.0 locale: en-us keywords: powershell,cmdlet title: about_Job_Details --- - # About Job Details # SHORT DESCRIPTION @@ -93,7 +92,7 @@ parameter of the Get-Job cmdlet. The IncludeChildJob parameter is introduced in Windows PowerShell 3.0. ```powershell -C:\PS> Get-Job -IncludeChildJob +PS> Get-Job -IncludeChildJob Id Name PSJobTypeName State HasMoreData Location Command -- ---- ------------- ----- ----------- -------- ------- @@ -107,7 +106,7 @@ value, use the ChildJobState parameter of the Get-Job cmdlet. The ChildJobState parameter is introduced in Windows PowerShell 3.0. ```powershell -C:\PS> Get-Job -ChildJobState Failed +PS> Get-Job -ChildJobState Failed Id Name PSJobTypeName State HasMoreData Location Command -- ---- ------------- ----- ----------- -------- ------- @@ -119,7 +118,7 @@ To get the child jobs of a job on all versions of Windows PowerShell, use the ChildJob property of the parent job. ```powershell -C:\PS> (Get-Job Job1).ChildJobs +PS> (Get-Job Job1).ChildJobs Id Name PSJobTypeName State HasMoreData Location Command -- ---- ------------- ----- ----------- -------- ------- @@ -131,7 +130,7 @@ You can also use a Get-Job command on the child job, as shown in the following command: ```powershell -C:\PS> Get-Job Job3 +PS> Get-Job Job3 Id Name PSJobTypeName State HasMoreData Location Command -- ---- ------------- ----- ----------- -------- ------- @@ -168,7 +167,7 @@ background jobs on the local computer and two remote computers. The command saves the job in the \$j variable. ```powershell -PS C:> $j = Invoke-Command -ComputerName localhost, Server01, Server02 ` +PS> $j = Invoke-Command -ComputerName localhost, Server01, Server02 ` -Command {Get-Date} -AsJob ``` @@ -177,7 +176,7 @@ shows that the command returned a job object with three child jobs, one for each computer. ```powershell -PS C:> $j | Format-List Name, ChildJobs +PS> $j | Format-List Name, ChildJobs Name : Job3 ChildJobs : {Job4, Job5, Job6} @@ -186,7 +185,7 @@ ChildJobs : {Job4, Job5, Job6} When you display the parent job, it shows that the job failed. ```powershell -C:\PS> $j +PS> $j Id Name PSJobTypeName State HasMoreData Location -- ---- ------------- ----- ----------- -------- @@ -197,7 +196,7 @@ But when you run a Get-Job command that gets the child jobs, the output shows that only one child job failed. ```powershell -PS C:> Get-Job -IncludeChildJobs +PS> Get-Job -IncludeChildJobs Id Name PSJobTypeName State HasMoreData Location Command -- ---- ------------- ----- ----------- -------- ------- @@ -212,9 +211,8 @@ the results of the parent job. But you can also get the results of a particular child job, as shown in the following command. ```powershell -C:\PS> Receive-Job -Name Job6 -Keep | Format-Table ComputerName, ->> DateTime -Auto - +PS> Receive-Job -Name Job6 -Keep | Format-Table ComputerName, +>> DateTime -AutoSize ComputerName DateTime ------------ -------- Server02 Thursday, March 13, 2008 4:16:03 PM @@ -282,7 +280,7 @@ instances of the scheduled job. Start a background job on the local computer. ```powershell -PS C:> Start-Job -Name LocalData {Get-Process} +PS> Start-Job -Name LocalData {Get-Process} Id Name PSJobTypeName State HasMoreData Location Command -- ---- ------------- ----- ----------- -------- ------- @@ -292,7 +290,7 @@ Id Name PSJobTypeName State HasMoreData Location Command Start a background job that runs on a remote computer. ```powershell -PS C:> Invoke-Command -ComputerName Server01 {Get-Process} ` +PS> Invoke-Command -ComputerName Server01 {Get-Process} ` -AsJob -JobName RemoteData Id Name PSJobTypeName State HasMoreData Location Command @@ -301,8 +299,9 @@ Id Name PSJobTypeName State HasMoreData Location Command ``` Create a scheduled job + ```powershell -PS C:> Register-ScheduledJob -Name ScheduledJob -ScriptBlock ` +PS> Register-ScheduledJob -Name ScheduledJob -ScriptBlock ` {Get-Process} -Trigger (New-JobTrigger -Once -At "3 PM") Id Name JobTriggers Command Enabled @@ -311,14 +310,16 @@ Id Name JobTriggers Command Enabled ``` Create a workflow. + ```powershell -PS C:> workflow Test-Workflow {Get-Process} +PS> workflow Test-Workflow {Get-Process} ``` Run the workflow as a job. + ```powershell -PS C:> Test-Workflow -AsJob -JobName TestWFJob +PS> Test-Workflow -AsJob -JobName TestWFJob Id Name PSJobTypeName State HasMoreData Location Command -- ---- ------------- ----- ----------- -------- ------- @@ -329,7 +330,7 @@ Get the jobs. The `Get-Job` command does not get scheduled jobs, but it gets instances of the scheduled job that are started. ```powershell -PS C:> Get-Job +PS> Get-Job Id Name PSJobTypeName State HasMoreData Location Command -- ---- ------------- ----- ----------- -------- ------- @@ -342,7 +343,7 @@ Id Name PSJobTypeName State HasMoreData Location Command To get scheduled jobs, use the Get-ScheduledJob cmdlet. ```powershell -PS C:> Get-ScheduledJob +PS> Get-ScheduledJob Id Name JobTriggers Command Enabled -- ---- ----------- ------- ------- @@ -359,7 +360,7 @@ Id Name JobTriggers Command Enabled [about_Scheduled_Jobs](../../psscheduledjob/about/about_scheduled_jobs.md) -[Invoke-Command](../Invoke-Command.md) +[Invoke-Command](../../Microsoft.PowerShell.Core/Invoke-Command.md) [Start-Job](../Start-Job.md) diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_Jobs.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_Jobs.md index d177d9c081c1..8f88bb08cdec 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_Jobs.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_Jobs.md @@ -1,11 +1,10 @@ ---- +--- ms.date: 11/29/2017 schema: 2.0.0 locale: en-us keywords: powershell,cmdlet title: about_Jobs --- - # About Jobs ## SHORT DESCRIPTION @@ -81,7 +80,7 @@ returns all of the jobs that were started in the current session. For example, the following command gets the jobs in the current session. ```powershell -PS C:> Get-Job +PS> Get-Job Id Name PSJobTypeName State HasMoreData Location Command -- ---- ------------- ----- ----------- -------- ------- @@ -165,14 +164,14 @@ The following commands show the results of `Receive-Job` commands run before the job is complete. ```powershell -C:\PS> Receive-Job -Job $job +PS> Receive-Job -Job $job Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName ------- ------ ----- ----- ----- ------ -- ----------- 103 4 11328 9692 56 1176 audiodg 804 14 12228 14108 100 101.74 1740 CcmExec -C:\PS> Receive-Job -Job $job +PS> Receive-Job -Job $job Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName ------- ------ ----- ----- ----- ------ -- ----------- @@ -190,14 +189,14 @@ The following commands show the effect of using the Keep parameter on a job that is not yet complete. ```powershell -C:\PS> Receive-Job -Job $job -Keep +PS> Receive-Job -Job $job -Keep Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName ------- ------ ----- ----- ----- ------ -- ----------- 103 4 11328 9692 56 1176 audiodg 804 14 12228 14108 100 101.74 1740 CcmExec -C:\PS> Receive-Job -Job $job -Keep +PS> Receive-Job -Job $job -Keep Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName ------- ------ ----- ----- ----- ------ -- ----------- @@ -253,7 +252,7 @@ for any of the jobs to be completed. The following command uses the Wait-Job cmdlet to wait for a job with ID 10. ```powershell -Wait-Job -ID 10 +Wait-Job -Id 10 ``` As a result, the PowerShell prompt is suppressed until the job is completed. @@ -264,7 +263,7 @@ expires, the command prompt returns, but the job continues to run in the background. ```powershell -Wait-Job -ID 10 -Timeout 120 +Wait-Job -Id 10 -Timeout 120 ``` ## STOPPING A JOB @@ -274,7 +273,7 @@ starts a job to get every entry in the System event log. It saves the job object in the \$job variable. ```powershell -$job = Start-Job -ScriptBlock {Get-EventLog -Log System} +$job = Start-Job -ScriptBlock {Get-EventLog -LogName System} ``` The following command stops the job. It uses a pipeline operator (|) to diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_Join.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_Join.md index 134c02f7aeae..e0624b2a124c 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_Join.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_Join.md @@ -1,11 +1,10 @@ ---- +--- ms.date: 06/09/2017 schema: 2.0.0 locale: en-us keywords: powershell,cmdlet title: about_Join --- - # About join ## SHORT DESCRIPTION diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_Language_Modes.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_Language_Modes.md index 9e468e91097f..4b9a9f28974f 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_Language_Modes.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_Language_Modes.md @@ -1,11 +1,10 @@ ---- +--- ms.date: 06/09/2017 schema: 2.0.0 locale: en-us keywords: powershell,cmdlet title: about_Language_Modes --- - # About Language Modes ## SHORT DESCRIPTION @@ -198,7 +197,7 @@ the session configuration has a LanguageMode property. You can find the language mode by getting the value of the LanguageMode property. ```powershell -PS C:\> (Get-PSSessionConfiguration -Name Test).LanguageMode +PS> (Get-PSSessionConfiguration -Name Test).LanguageMode FullLanguage ``` @@ -215,7 +214,7 @@ state. For example: ```powershell -PS C:> $ExecutionContext.SessionState.LanguageMode +PS> $ExecutionContext.SessionState.LanguageMode ConstrainedLanguage ``` diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_Line_Editing.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_Line_Editing.md index 8c20f873f9cb..826d88140b78 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_Line_Editing.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_Line_Editing.md @@ -1,12 +1,12 @@ ---- +--- ms.date: 06/09/2017 schema: 2.0.0 locale: en-us keywords: powershell,cmdlet title: about_Line_Editing --- - # About Line Editing + ## about_Line_Editing @@ -35,6 +35,7 @@ To delete the character in front of the cursor, press the DELETE key. Delete the Remainder of a Line To delete all the characters in the line after the cursor, press + # CTRL+END. diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_locations.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_locations.md index 82f97c6de5b4..c0ee99bbcd73 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_locations.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_locations.md @@ -1,11 +1,10 @@ ---- +--- ms.date: 06/09/2017 schema: 2.0.0 locale: en-us keywords: powershell,cmdlet title: about_Locations --- - # about_Locations ## SHORT DESCRIPTION diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_logical_operators.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_logical_operators.md index b3ae17b9ddb5..47a7d8391f41 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_logical_operators.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_logical_operators.md @@ -1,11 +1,10 @@ ---- +--- ms.date: 01/03/2018 schema: 2.0.0 locale: en-us keywords: powershell,cmdlet title: about_Logical_Operators --- - # about_Logical_Operators ## SHORT DESCRIPTION From 1aa6fa1fb8a8e4e32df00766fb59c1563429a70b Mon Sep 17 00:00:00 2001 From: Bobby Reed Date: Mon, 30 Apr 2018 08:32:51 -0400 Subject: [PATCH 2/2] Fixing two broken links that were broken by my code --- reference/3.0/Microsoft.PowerShell.Core/About/about_History.md | 2 +- .../3.0/Microsoft.PowerShell.Core/About/about_Job_Details.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_History.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_History.md index 7ffe365673d7..e814fad1adce 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_History.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_History.md @@ -87,5 +87,5 @@ are completed only when you exit the prompt level.) - [about_Line_Editing](about_Line_Editing.md) - [about_Preference_Variables](about_Preference_Variables.md) -- [about_Profiles](http://go.microsoft.com/fwlink/?LinkID=113729) +- [about_Profiles](about_Profiles.md) - [about_Variables](about_Variables.md) \ No newline at end of file diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_Job_Details.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_Job_Details.md index 7f3def34c33a..a7328b50a552 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_Job_Details.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_Job_Details.md @@ -360,7 +360,7 @@ Id Name JobTriggers Command Enabled [about_Scheduled_Jobs](../../psscheduledjob/about/about_scheduled_jobs.md) -[Invoke-Command](../../Microsoft.PowerShell.Core/Invoke-Command.md) +[Invoke-Command](../Invoke-Command.md) [Start-Job](../Start-Job.md)