This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 8dc895cbb6 Few doc fixes - links, grammer and wording (#31719)
8dc895cbb6 is described below
commit 8dc895cbb64e991893705b04e03a6655c35888fe
Author: Akash Sharma <[email protected]>
AuthorDate: Tue Jun 6 03:05:08 2023 +0530
Few doc fixes - links, grammer and wording (#31719)
* fix-docs
* Update BREEZE.rst
---
BREEZE.rst | 3 +--
docs/apache-airflow/howto/custom-operator.rst | 2 +-
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/BREEZE.rst b/BREEZE.rst
index 5994cea06a..e897493862 100644
--- a/BREEZE.rst
+++ b/BREEZE.rst
@@ -884,8 +884,7 @@ To run the whole test class:
You can re-run the tests interactively, add extra parameters to pytest and
modify the files before
re-running the test to iterate over the tests. You can also add more flags
when starting the
``breeze shell`` command when you run integration tests or system tests. Read
more details about it
-in the ``TESTING.rst <TESTING.rst#>`` where all the test types of our are
explained and more information
-on how to run them.
+in the `testing doc <TESTING.rst>`_ where all the test types and information
on how to run them are explained.
This applies to all kind of tests - all our tests can be run using pytest.
diff --git a/docs/apache-airflow/howto/custom-operator.rst
b/docs/apache-airflow/howto/custom-operator.rst
index bd80913a25..8021b84fcd 100644
--- a/docs/apache-airflow/howto/custom-operator.rst
+++ b/docs/apache-airflow/howto/custom-operator.rst
@@ -87,7 +87,7 @@ can be reused by other users in different operators. Such
approach provides bett
utilization of added integration than using ``CustomServiceBaseOperator`` for
each external service.
Other consideration is the temporary state. If an operation requires an
in-memory state (for example
-a job id that should be used in ``on_kill`` method to cancel a request) then
the state should be keep
+a job id that should be used in ``on_kill`` method to cancel a request) then
the state should be kept
in the operator not in a hook. In this way the service hook can be completely
state-less and whole
logic of an operation is in one place - in the operator.
