Skip to content
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

Docs/clarify connect language 2 backport 1.15 #17233

Conversation

jkirschner-hashicorp
Copy link
Contributor

@jkirschner-hashicorp jkirschner-hashicorp commented May 5, 2023

Replaces #17227.

Backport #17222 to 1.15.
Also includes a follow-up misspelling correction (for which there's a PR against main: #17229).

@jkirschner-hashicorp jkirschner-hashicorp added type/docs Documentation needs to be created/updated/clarified pr/no-changelog PR does not need a corresponding .changelog entry pr/no-backport labels May 5, 2023
@jkirschner-hashicorp jkirschner-hashicorp requested a review from a team as a code owner May 5, 2023 22:40
@hashicorp-cla
Copy link

hashicorp-cla commented May 5, 2023

CLA assistant check
All committers have signed the CLA.

Remove outdated usage of "Consul Connect" instead of Consul service mesh.

The connect subsystem in Consul provides Consul's service mesh capabilities.
However, the term "Consul Connect" should not be used as an alternative to
the name "Consul service mesh".
@jkirschner-hashicorp jkirschner-hashicorp force-pushed the docs/clarify-connect-language-2-backport-1.15 branch from f6f0e9d to fcd36b2 Compare May 5, 2023 22:46
@jkirschner-hashicorp jkirschner-hashicorp merged commit b99de08 into release/1.15.x May 8, 2023
@jkirschner-hashicorp jkirschner-hashicorp deleted the docs/clarify-connect-language-2-backport-1.15 branch May 8, 2023 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/no-backport pr/no-changelog PR does not need a corresponding .changelog entry type/docs Documentation needs to be created/updated/clarified
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants