I would start with double checks on spelling ... /s
Seriously, a typo can happen to everyone, but when they happen, particularly in short text or in a title they immediately give (at least to me) the impression that there has not been enough attention/diligence, which is not a good sign, particularly for technical writers.
When the phone rings, always answer and say "Yes."
When you get big, hire other writers to maintain the "Yes."
That's what a B2B brand is.
[\Metaphor]
Good luck.
There are many small open source projects that could use a technical writer’s help.
I would image these thngs could be useful: Write a newsletter, give conference talks, build a portfolio. Write a book. Use social media if you’re into that kind of stuff. (Instagram, YouTube, Mastodon, whatever suits you.) Have a website/blog for your longform articles on the subject.
HTH, good luck!
PS.
Be persistent and be patient. Set realistic goals so that you will not burn out and don’t be too dissapointed if it doesn’t go as fast as you would like.
For a given time frame, i.e. a year or so, it’s probably not possible to be prolific in all the areas I mentioned. So maybe pick 1-3 areas and focus on them, based on what you would find most fun.