Move paragraph to end

Author: camelid

posts/inside-rust/2020-10-08-regression-labels.md

@@ -1,8 +1,8 @@
 ---
 layout: post
 title: "Marking issues as regressions"
-author: Camelid
 description: "Now anyone can mark issues as regressions!"
+author: Camelid
 team: the release team <https://www.rust-lang.org/governance/teams/operations#release>
 ---
 
@@ -35,14 +35,14 @@ regression and it will automatically be prioritized:
 Just replace `{release-channel}` with one of `nightly`, `beta`, or `stable`,
 depending on when the regression occurred, and you're good to go!
 
-We really appreciate it if you mark all regressions with an appropriate label
-so we can track them and fix them as soon as possible!
-
 Finally, if you have an issue that is *not* a regression, but is still something
 that is important to be fixed, you can request prioritization with:
 
 > @**rustbot** prioritize
 
+We really appreciate it if you mark all regressions with an appropriate label
+so we can track them and fix them as soon as possible!
+
 [rustbot-labeling-docs]: https://rustc-dev-guide.rust-lang.org/rustbot.html#issue-relabeling
 [internals-thread]: https://internals.rust-lang.org/t/1-46-is-unusable-for-me-solved/13161/10
 [regression-label-pr]: https://github.com/rust-lang/rust/pull/77555