How do you keep documentation up to date with rapid changes in DevOps infrastructure

How do you keep documentation up to date with rapid changes in DevOps infrastructure?

DevOps infrastructures tend to be dynamic and rapidly changing; documentation has to be maintained regularly in order to reflect the changing situation. I would want to know in this question how you ensure that documentation stays up-to-date, how you manage the changes, how you involve the team in the effort, and what automation or tools (like wikis, code comments, or some form of Git-based documentation) you might use in order to maintain current information and accessibility in the configurations, tools, and practice.