This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch v2-3-test
in repository https://gitbox.apache.org/repos/asf/airflow.git

commit e8c95a237bf5e6b7fbd9b3e7ae085e4acded40e7
Author: Edith Puclla <[email protected]>
AuthorDate: Thu May 5 10:06:35 2022 -0500

    Changed word 'the' instead 'his' (#23493)
    
    (cherry picked from commit ed0f8a745e8dbe25ac45318c0c0d5f5ccda67356)
---
 dev/breeze/doc/adr/0012-asking-user-for-confirmation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev/breeze/doc/adr/0012-asking-user-for-confirmation.md 
b/dev/breeze/doc/adr/0012-asking-user-for-confirmation.md
index 6b63780b23..82dd2df35b 100644
--- a/dev/breeze/doc/adr/0012-asking-user-for-confirmation.md
+++ b/dev/breeze/doc/adr/0012-asking-user-for-confirmation.md
@@ -53,7 +53,7 @@ In case 1) - we should present the user with information on 
what is going to cha
 not be surprised with the effect of it.
 
 In case 2) - we should not break the workflow of the user, unless this is 
really necessary or the user
-chooses to break his workflow. This is important in situation when the user 
needs to perform an action
+chooses to break the workflow. This is important in situation when the user 
needs to perform an action
 quickly and disrupting the workflow would be annoying and undesired. In this 
case the confirmation of
 the "long" action should not be "necessary" - when user does not expect the 
action to wait for confirmation.
 

Reply via email to