Updating v2_18_5.md file and other files

[ArooshLele]

Describe your pull request here:
Added content in v2_18_6.md
List the file(s) included in this PR: v2_18_6.md

[github-actions]

😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.

• Add the label review: doc.
• Identify your content topic with a label. (Examples: area: apiml, area: cli, area: install and config, etc.)
• Specify the major Zowe release(s) for your content. (Examples: release: V1, release: V2, release: V3)
  • If adding content that needs to be removed from V3 documentation, add the V3 N/A tag.
• Select the master branch if your PR updates content that is on the live site. Select docs-staging if your PR updates content for a future release.
• Notify the Doc Squad about this PR. If you don't know whom should review your content, message the #zowe-doc Slack channel. If you know which Doc Squad writer should approve your content, add that person as a reviewer.

Need help? Contact the Doc Squad in the #zowe-doc Slack channel.

[github-actions]

😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.

• Add the label review: doc.
• Identify your content topic with a label. (Examples: area: apiml, area: cli, area: install and config, etc.)
• Specify the major Zowe release(s) for your content. (Examples: release: V1, release: V2, release: V3)
  • If adding content that needs to be removed from V3 documentation, add the V3 N/A tag.
• Select the master branch if your PR updates content that is on the live site. Select docs-staging if your PR updates content for a future release.
• Notify the Doc Squad about this PR. If you don't know whom should review your content, message the #zowe-doc Slack channel. If you know which Doc Squad writer should approve your content, add that person as a reviewer.

Need help? Contact the Doc Squad in the #zowe-doc Slack channel.

[github-actions]

😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.

• Add the label review: doc.
• Identify your content topic with a label. (Examples: area: apiml, area: cli, area: install and config, etc.)
• Specify the major Zowe release(s) for your content. (Examples: release: V1, release: V2, release: V3)
  • If adding content that needs to be removed from V3 documentation, add the V3 N/A tag.
• Select the master branch if your PR updates content that is on the live site. Select docs-staging if your PR updates content for a future release.
• Notify the Doc Squad about this PR. If you don't know whom should review your content, message the #zowe-doc Slack channel. If you know which Doc Squad writer should approve your content, add that person as a reviewer.

Need help? Contact the Doc Squad in the #zowe-doc Slack channel.

[github-actions]

⚠️ Looks like something is wrong with the PR description. Remember to add a description and the file(s) included in this PR.

If you have addressed this issue already, refresh this page in your browser to remove this comment.

[github-actions]

⚠️ Looks like something is wrong with the PR description. Remember to add a description and the file(s) included in this PR.

If you have addressed this issue already, refresh this page in your browser to remove this comment.

[github-actions]

⚠️ Looks like something is wrong with the PR description. Remember to add a description and the file(s) included in this PR.

If you have addressed this issue already, refresh this page in your browser to remove this comment.

[anaxceron]

@ArooshLele -- please update the release notes in the other versioned (3.1-3.4) release notes folders. When you do so, I will approve this PR.

[github-actions]

🚀 Deployed on https://6a639e72e7798016543f11b8--zowe-docs-master.netlify.app

[anaxceron]

@ArooshLele -- Also, are you sure your notes belong to the 2.18.6 release notes, and not 2.18.5? The 2.18.6 release is client-side only, so I would assume that any server sider updates should only go in the 2.18.5. In V2, client and server components are out of sync w/ their releases. Client side components are ahead by one release.
But you know best so I leave it up to you.

[anaxceron]

And one last thing! Please update the release notes in the v2.18.x versioned doc.
apologies for the crazy amount of comments! 😵

[ArooshLele]

@ArooshLele -- please update the release notes in the other versioned (3.1-3.4) release notes folders. When you do so, I will approve this PR.

Hi @anaxceron done.

[anaxceron]

Hi @ArooshLele.

What I meant by "versioned (3.1-3.4) release notes folders" were these locations:

https://docs.zowe.org/v3.4.x/whats-new/release-notes/v2_18_5/
https://docs.zowe.org/v3.3.x/whats-new/release-notes/v2_18_5/
https://docs.zowe.org/v3.2.x/whats-new/release-notes/v2_18_5/
https://docs.zowe.org/v3.1.x/whats-new/release-notes/v2_18_5/
https://docs.zowe.org/v2.18.x/whats-new/release-notes/v2_18_5/

Right now, if I go to v3.2 of the doc site in this PR's build, I don't see the notes you added for v2.18.5.

It's important that our release notes match all across our doc site versions (the versions that a reader selects from in the top-right version picker drop-down menu). The way to do that is to add the same updates to the vX.XX.x folders in the versioned_docs directory (2.18.x-3.4.x, excluding v3.0.0 b/c it's been archived and is no longer available on the version picker).

I see that you're making lots of changes beyond modifications to the v2.18.5 notes. Please confirm that these changes are also included in the versioned doc sites/folders listed above.

Once all your changes have been added to all the versions of the doc site, I can approve this PR. Let me know if you'd like to get a call to discuss this.