Sorry about that! Unfortunately documentation will always follow behind engine releases, especially here on the bleeding edge releases. In this case, I wasn’t even aware that a PR to disable WP had made it in to 5.2, but in this case we’ll have to submit a bug report.