From ebe32840377b4af3b3e1a20a3603439fb8a46153 Mon Sep 17 00:00:00 2001 From: On Freund Date: Wed, 22 Mar 2023 18:59:29 +0200 Subject: [PATCH] Fix typo in review process (#1724) --- docs/review-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/review-process.md b/docs/review-process.md index c562bbd6..4cf05176 100644 --- a/docs/review-process.md +++ b/docs/review-process.md @@ -235,7 +235,7 @@ each time you go through the process. just comment that. By responding to the bot, it will know things are not stale and will back off. In the mean time, it might be a good idea to rebase your PR on the latest development branches to ensure you are fully - catched up with recent changes. + caught up with recent changes. 5. **I have a PR that should go into a hotfix/patch release, how do I do that?** Just create the PR as normal, and make it very clear in the PR description