<!-- https://docs.google.com/document/d/1MddE2otY6hrwQAtmjgXhpQp6BRXbv8fdCf4EX6dIapA/edit#heading=h.m52rdgevmfw1 --> Getting docs tested How to swim in the deep water - A lone writer’s guide to survival Starting notes: Why should documentation be tested? How is this different than a content review? Who should test it? How to implement a procedure where SMEs (developers, support) test the procedures/info in the docs? Hack-a-thon content: