Remove leftovers in the LXD book

[bertronika]

This pull request removes some left-over text in the LXD book, which breaks formatting on the web page and confuses the reader. I've also added a missing dot on the landing README.md - a minor change that does not warrant a separate request.

Author checklist (Completed by original Author)

• Good fit for the Rocky Linux project? Title and Author Metatags inserted ?
• If applicable, steps and instructions have been tested to work
• Initial self-review to fix basic typos and grammar completed

Rocky Documentation checklist (Completed by Rocky team)

• 1st Pass (Document is good fit for project and author checklist completed)
• 2nd Pass (Technical Review - check for technical correctness)
• 3rd Pass (Detailed Editorial Review and Peer Review)
• Final approval (Final Review)

[github-actions]

Test results for 9292f74:

Number of broken URLs: 0

URL,RESULT,FILENAME

[wsoyinka]

Reason for deletion in 03-lxdinit.md is not clear.

[bertronika]

This is the current state (https://docs.rockylinux.org/books/lxd_server/03-lxdinit/):

The "Trust password for new clients:" text should appear only once, after setting the address and port for the snapshot server. It is duplicated after the YAML section, along with the trust password explanation.

Furthermore, the erroneous backticks prevent the sentence "Setting Up User Privileges" appearing as a heading, and break the rendering of everything that follows (code blocks and paragraphs are reversed).

[sspencerwire]

@bertronika Thank you for this PR. The way your explanation was worded, didn't quite convince those reviewing the PR, but I could physically see the problem you were reporting by pulling up the page in a browser. The trust password section duplicated and the code block backticks are in the incorrect order. I'll go ahead and reopen the PR and merge it. We DO definitely appreciate your review and correction!!

[sspencerwire]

@all-contributors please add @bertronika for content

[allcontributors]

@sspencerwire

I've put up a pull request to add @bertronika! 🎉

[bertronika]

The way your explanation was worded ...

I've figured that I should have put the screenshot and better explanation in the first post. I'm glad we got it resolved.