Skip to content

Enter-PSSession - Fix example 7 description #9128

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 16, 2022

Conversation

ClaudioESSilva
Copy link
Contributor

@ClaudioESSilva ClaudioESSilva commented Aug 16, 2022

Make the description clear.
Example 7 is not using -Port parameter but rather infers that from the -HostName parameter.

PR Summary

PR Checklist

  • Descriptive Title: This PR's title is a synopsis of the changes it proposes.
  • Summary: This PR's summary describes the scope and intent of the change.
  • Contributor's Guide: I have read the contributors guide.
  • Style: This PR adheres to the style guide.

Not using `-Port` parameter but infer that from the `-HostName` parameter.
@github-actions
Copy link

Expectations

Thanks for your submission! Here's a quick note to provide you with some context for what to expect from the docs team and the process now that you've submitted a PR. Even if you've contributed to this repo before, we strongly suggest reading this information; it might have changed since you last read it.

To see our process for reviewing PRs, please read our editor's checklist and process for managing pull requests in particular. Below is a brief, high-level summary of what to expect, but our contributor guide has expanded details.

The docs team begins to review your PR if you request them to or if your PR meets these conditions:

  • It is not a draft PR.
  • It does not have a WIP prefix in the title.
  • It passes validation and build steps.
  • It does not have any merge conflicts.
  • You have checked every box in the PR Checklist, indicating you have completed all required steps and marked your PR as Ready to Merge.

You can always request a review at any stage in your authoring process, the docs team is here to help! You do not need to submit a fully polished and finished draft; the docs team can help you get content ready for merge.

While reviewing your PR, the docs team may make suggestions, write comments, and ask questions. When all requirements are satisfied, the docs team marks your PR as Approved and merges it. Once your PR is merged, it is included the next time the documentation is published. For this project, the documentation is published daily at 3 p.m. Pacific Standard Time (PST).

@opbld32
Copy link

opbld32 commented Aug 16, 2022

Docs Build status updates of commit 8ee0bf8:

✅ Validation status: passed

File Status Preview URL Details
reference/7.2/Microsoft.PowerShell.Core/Enter-PSSession.md ✅Succeeded View (powershell-7.2)

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

@opbld33
Copy link

opbld33 commented Aug 16, 2022

Docs Build status updates of commit da4f5c3:

✅ Validation status: passed

File Status Preview URL Details
reference/5.1/Microsoft.PowerShell.Core/Enter-PSSession.md ✅Succeeded View (powershell-5.1)
reference/7.0/Microsoft.PowerShell.Core/Enter-PSSession.md ✅Succeeded View (powershell-7)
reference/7.2/Microsoft.PowerShell.Core/Enter-PSSession.md ✅Succeeded View (powershell-7.2)
reference/7.3/Microsoft.PowerShell.Core/Enter-PSSession.md ✅Succeeded View (powershell-7.3)

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

@sdwheeler sdwheeler merged commit 15c991d into MicrosoftDocs:main Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants