!722 (and more specifically ae7f4fa8 and
cc14903c) updated this page's title.
And then we tagged this scenario fragile due to #18852, which lead us to
incorrectly believe that any failure in that step was caused by that unrelated
test suite robustness issue.
