Remove duplicate subchapter

[jenting]

Make sure it's tested

Technical writers will not always be able to verify the implementation!

Any PR opened is assumed to have been verified by QA if not designated by comments or labels otherwise. Please make sure you have tested the changes and included any information that a user would require to use the documentation.

Describe your changes

Remove duplicate subchapter.

Related Issues / Projects

Please provide links to Bugzilla and other GitHub projects with your description if they are related to the changes.

Relates to:

Enable maintainer updates

Please enable maintainer updates so we can push commits into your branch to make collaboration and reviews easier.

Do not force push your branch

Please avoid force pushing to branches that are subject of pull requests. Force pushing breaks maintainer commits in many cases and is very hard (if not impossible) to untangle for backporting.

Labels

Please set any (and all) appropriate labels that describe the status of the PR.

Label	Description
P1	PR should be worked on and merged as soon as possible
Blocked	Work can not proceed because other work has not been completed, PR can not be merged (code has not been merged but documentation is ready)
On-Hold	Underlying work is completed but the PR should not be merged
ReleaseNotes	User interaction is required after the introduction of this change and the change must be mentioned in the release notes
v3/v4/v4.x	Which version of the release the PR should be merged into, this can be multiple versions, please set the "Backport" label if it needs to go into a previous release
Needs Review	Some details of the PR are known to be incomplete and must be discussed with other engineers before merging (if possible assign reviewers or cc mention in comments), PR can not be merged

Signed-off-by: JenTing Hsiao jenting.hsiao@suse.com

[nkoranova]

Thanks!