From d17b380653da5f95885ce53468fe7aac60672841 Mon Sep 17 00:00:00 2001 From: Adam Johnson Date: Fri, 1 May 2020 13:37:21 +0100 Subject: Refs #30573 -- Rephrased "Of Course" and "Obvious(ly)" in documentation and comments. --- docs/internals/contributing/writing-code/submitting-patches.txt | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'docs/internals/contributing/writing-code') diff --git a/docs/internals/contributing/writing-code/submitting-patches.txt b/docs/internals/contributing/writing-code/submitting-patches.txt index 5ea265c55b..45b2b9bdc4 100644 --- a/docs/internals/contributing/writing-code/submitting-patches.txt +++ b/docs/internals/contributing/writing-code/submitting-patches.txt @@ -82,15 +82,14 @@ As always, more communication is better than less communication! Which tickets should be claimed? -------------------------------- -Of course, going through the steps of claiming tickets is overkill in some -cases. +Going through the steps of claiming tickets is overkill in some cases. In the case of small changes, such as typos in the documentation or small bugs that will only take a few minutes to fix, you don't need to jump through the hoops of claiming tickets. Submit your patch directly and you're done! -Of course, it is *always* acceptable, regardless whether someone has claimed it -or not, to submit patches to a ticket if you happen to have a patch ready. +It is *always* acceptable, regardless whether someone has claimed it or not, to +submit patches to a ticket if you happen to have a patch ready. .. _patch-style: -- cgit v1.3