Updated the structure and applied feedback

[Felonious-Spellfire]

What does this PR do?

Modifies the content for Encrypted Secrets.

Does your PR introduce any breaking changes? If yes, please list them.

None

Before submitting

• Was this discussed/approved via a GitHub issue? (not for typos and docs)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure your PR does only one thing, instead of bundling different changes together?
• Did you make sure to update the documentation with your changes? (if necessary)
• Did you write any new necessary tests? (not for typos and docs)
• Did you verify new and existing tests pass locally with your changes?
• Did you list all the breaking changes introduced by this pull request?
• Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review

Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

• Is this pull request ready for review? (if not, please submit in draft mode)
• Check that all items from Before submitting are resolved
• Make sure the title is self-explanatory and the description concisely explains the PR
• Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

Make sure you had fun coding 🙃

[edenlightning]

We should also add this to the menu in how to "Add a secret"

[krishnakalyan3]

@alecmerdler @nohalon should we mention in the doc somewhere that _ are not supported?

[Felonious-Spellfire]

@alecmerdler @nohalon should we mention in the doc somewhere that _ are not supported?

We do:

Secret names must start with a letter and can only contain letters, numbers, dashes, and periods.