sops: update page

[Shensen1]

Hi,
my first public contribution here, so greetings to my Ma! :)

I think this one is essential, got stuck twice now by remembering this one and so I guess it should be shared with others

• The page(s) are in the correct platform directories: common, linux, osx, windows, sunos, android, etc.
• The page(s) have at most 8 examples.
• The page description(s) have links to documentation or a homepage.
• The page(s) follow the content guidelines.
• The PR title conforms to the recommended templates.
• Version of the command being documented (if known):

[CLAassistant]

All committers have signed the CLA.

[Shensen1]

Ok, nice So now just wait for another ok and then it gets pushed? @Magrid0

But why have the file paths to be in that format? actually wanted to add one simpler syntax example

[Magrid0]

Ok, nice So now just wait for another ok and then it gets pushed?

Yep!

But why have the file paths to be in that format? actually wanted to add one simpler syntax example

Because the Style Guide say they have to be written in this way

[Shensen1]

Ok, makes sense, head guidelines in mind with

2. When in doubt, keep new command-line users in mind. Err on the side of clarity rather than terseness. For example, commands that require sudo should include it directly in the examples.

[kbdharun]

Welcome to tldr and thanks for your contribution. LGTM, after @sebastiaanspeck's suggestion above.

[Magrid0]

LGTM, i think it'll be ready to merge after sebastiaanspeck suggestion

[spageektti]

Since the author of this PR has been inactive for a long time, I have made the suggested changes.

Maintainers Guide says:

If the only issues holding up a merge are trivial fixes
(typos, syntax errors, etc.), and the author doesn't respond in a day or two,
maintainers can make the necessary changes themselves,
and proceed with the merge process.

[sebastiaanspeck]

LGGM, after the suggestions are fixed