Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Nov 26, 2024

Fixes #6170 — minor changes on several pages. We are no longer providing only "Native" cloud security (we're using 3rd party data as well as providing our own integrations). This PR updates language on several pages accordingly. Please refer to the diff for changes.


This is an automatic backport of pull request #6175 done by Mergify.

* Updates "Cloud native security" to "Cloud security"

* incorporates Smriti's and Nick's reviews

* Capitalizes S in Security

(cherry picked from commit 863c54f)

# Conflicts:
#	docs/serverless/cloud-native-security/cloud-native-security-overview.asciidoc
#	docs/serverless/security-overview.asciidoc
@mergify mergify bot requested a review from a team as a code owner November 26, 2024 22:27
@mergify
Copy link
Contributor Author

mergify bot commented Nov 26, 2024

Cherry-pick of 863c54f has failed:

On branch mergify/bp/8.17/pr-6175
Your branch is up to date with 'origin/8.17'.

You are currently cherry-picking commit 863c54f9.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   docs/cloud-native-security/cloud-native-security-index.asciidoc
	modified:   docs/es-overview.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/serverless/cloud-native-security/cloud-native-security-overview.asciidoc
	deleted by us:   docs/serverless/security-overview.asciidoc

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@github-actions
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@benironside benironside enabled auto-merge (squash) November 26, 2024 23:03
@benironside benironside merged commit f32f68a into 8.17 Nov 26, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants