-
Notifications
You must be signed in to change notification settings - Fork 16
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
[DOC] Edit backuprestore content initial #21
Conversation
…nd content restructuring/granulation.
Co-authored-by: Thomas Polkowski <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
||
## Usage | ||
Backups can be created using `mkectl backup create --name <name>`. | ||
>The offered instructions assume that you have created a cluster and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should it be commented?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my opinion, yes, this type of content should usually be set apart from the main textual flow in some manner.
Merge branch 'edit-backuprestore-content-initial' of github.com:Mirantis/mke-docs into edit-backuprestore-content-initial
Co-authored-by: Kory <[email protected]>
…nd content restructuring/granulation.
… by conflict resolution operation.
Initial edit of MKE 4 backuprestore content, including text changes and content restructuring/granulation.