Openshot-qt: User manual content

[ferdnyc]

While glancing over the Developers section of the User Guide, I happened to notice this passage, in particular the first sentence of the second paragraph:

_*cough*_ _Ahem..._

While in some ways I appreciate the brutal honesty there, we should probably fix that.

More practically, I noticed there were places where the Guide directs the user to some directory location under /.openshot_qt/..., which is just _wrong_. ($HOME/.openshot_qt/... or ~/.openshot_qt/..., sure, that's acceptable, and even correct outside of Windows. But /.openshot_qt/ is a very different thing.)

All of which is to say, #2989 is still open, and would clearly benefit from some attention.

[N3WWN]

(Sorry, couldn't resist!)

[DylanC]

@ferdnyc - I'm still lurking in the shadows following this project btw. 😄 I remember at one point I was thinking @N3WWN would be a great person for Docs. I could see from his responses to issues that he has fantastic knowledge of OpenShot from a users perspective and has technical knowledge too. 👍

[ferdnyc]

Absolutely! Hell, if ego-stroking is fair game, it is obvious to anyone who interacts with @N3WWN that they are dealing with a hoopy frood who always knows where his towel is.

[stale[bot]]

Thank you so much for submitting an issue to help improve OpenShot Video Editor. We are sorry about this, but this particular issue has gone unnoticed for quite some time. To help keep the OpenShot GitHub Issue Tracker organized and focused, we must ensure that every issue is correctly labelled and triaged, to get the proper attention.
This issue will be closed, as it meets the following criteria: - No activity in the past 180 days - No one is assigned to this issue
We'd like to ask you to help us out and determine whether this issue should be reopened. - If this issue is reporting a bug, please can you attempt to reproduce on the latest daily build to help us to understand whether the bug still needs our attention. - If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant.
Thanks again for your help!