Update create.asciidoc

[SutraHsing]

Summary

Summarize your PR. If it involves visual changes include a screenshot or gif.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser
• This was checked for cross-browser compatibility, including a check against IE11

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[kibanamachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[cla-checker-service]

💚 CLA has been signed

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[elasticmachine]

Pinging @elastic/kibana-docs (Team:Docs)

[KOTungseth]

LGTM

[KOTungseth]

@SutraHsing before you can merge this PR, you'll need to sign the contributor agreement.

[SutraHsing]

I'm a newbie in contributing code. Glad to sign a contributor agreement!

[rudolf]

@SutraHsing I see you're targeting the 7.8 branch. Unless the fix is version specific, we usually target the master branch and then backport it to the different version branches as required. I'll see if I'm able to change this PR, but if it doesn't work you might have to open a new PR.

[rudolf]

I don't think there's a super straight-forward way to change the target of this PR. Could you please do the following to create a new branch off of master apply your changes there and create a new PR from that...

In your local clone of your Kibana fork:

1. git checkout master
2. git checkout -b update-saved-objects-docs (or any branch name you want to use)
3. git cherry-pick 4b4967f (cherry pick your commit to this new branch)
4. git push
5. Open a new PR targeting master
6. Add the same labels as this PR and close this PR