@BaToolo
It doesn't take much to do a good job. If you're doing this for you, and you're doing it for free, then there's no rush. No deadline.
So why release something subpar? If you don't have a lot of skill, then spend more time refining your work, or learning. If you're new, or don't understand something, or simply just don't know something, ask someone. Research and learn.
If you believe "this is enough of a good product to not put any shame on any people that worked on this."
Then I think your bar is set too low. There's a number of glaring, easily fixed issues, that aren't nitpicky in the slightest.
It's an improvement over the original release, but is it good? Not really. It's below average. That doesn't mean you need to give up or anything, it just means you need to learn from your mistakes and do better.
On a somewhat different topic, a proofreader should be a native speaker of the target language, with substantial experience and a superior grasp over nuance. That's not always achievable, but it doesn't mean you can't ask for help from someone else.