The goal of any documentation is to help people. "Good" documentation is useful. "Bad" documentation confuses readers and might physically harm people or damage equipment.
Also, when writing documentation, consistency is quite important. Often this is resolved with something known as a style guide. Style guides might be formal or informal. I think that point 3 in this article mentions it quite well.
Java is the backbone of so many enterprise apps out there. It’s got a lot of momentum. While I prefer the syntax of other languages I could easily see my knowledge of Java/spring being a value add the rest of my career