[ozone] branch master updated: update readme (#4535)

[ri...@apache.org]

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

ritesh pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ozone.git


The following commit(s) were added to refs/heads/master by this push:
     new 53d8fe0e57 update readme (#4535)
53d8fe0e57 is described below

commit 53d8fe0e57f644989da927b65d00fecdbbfc4138
Author: Ethan Rose <33...@users.noreply.github.com>
AuthorDate: Wed Apr 5 23:29:46 2023 -0700

    update readme (#4535)
---
 hadoop-ozone/dist/src/main/compose/upgrade/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/hadoop-ozone/dist/src/main/compose/upgrade/README.md b/hadoop-ozone/dist/src/main/compose/upgrade/README.md
index 78a5b0e670..49c453800e 100644
--- a/hadoop-ozone/dist/src/main/compose/upgrade/README.md
+++ b/hadoop-ozone/dist/src/main/compose/upgrade/README.md
@@ -23,7 +23,7 @@ an older release of Ozone and a later release (which may be the local build).
 - The whole test matrix of upgrading and downgrading to/from previous releases to the current code is too time consuming to do on every CI run. Instead we recommend release managers manually test the full matrix before each release, and let only the tests from the previous release to the current code be run in CI.
 
 1. Before the release, test the whole matrix of upgrades from the previous version to the version you are releasing.
-    - This is important manual verification that the release does not break backwards compatibility, and the results can be included in the release vote mailing thread.
+    - This is important to manually verify that the release does not break backwards compatibility. The results can be included in the release vote mailing thread.
     - To do this, uncomment all lines that contain `run_test` in the *test.sh* file, and execute *test.sh* either locally or on GitHub actions.
 
 2. After the release is finished and its docker image is published, add the new version to the test matrix.
@@ -36,7 +36,7 @@ an older release of Ozone and a later release (which may be the local build).
 - These tests will not catch backwards incompatible changes against commits in between releases.
     - Example:
         1. After 1.2.0, a change *c1* is made that is backwards compatible with 1.2.0.
-        2. After *c1*, a new change *c2* is made that is also backwards compatible with 1.0.0 but backwards *incompatible* with *c1*.
+        2. After *c1*, a new change *c2* is made that is also backwards compatible with 1.2.0 but backwards *incompatible* with *c1*.
 
         - This test suite will not raise an error for *c2*, because it only tests against the last release
         (1.2.0), and not the last commit (*c1*).


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@ozone.apache.org
For additional commands, e-mail: commits-help@ozone.apache.org