Spot what’s wrong with how this feature got documented

We’ve built an online exercise: Three teams. Three sets of docs for the same feature. Zero agreement on which one is correct. See if you can spot where this documentation process falls apart?

The exercise is embedded below or you can use this link to the exercise.

Categories: API

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.