Clarify the target of the events redesign discussion at ESC
Following the conversation [1] on the mailing list, add an extra
clarification on which version will be targeted by Luca and his
GerritForge team for the event system evolution in Gerrit.
Also remove redundant indenting on the corresponding paragraph.
[1] https://groups.google.com/g/repo-discuss/c/027jSo80M30
Change-Id: Icea98dca793b567ff4019b3e892b1adefb99a7f6
diff --git a/_posts/2021-03-09-esc-minutes.md b/_posts/2021-03-09-esc-minutes.md
index 14821bb..d21213a 100644
--- a/_posts/2021-03-09-esc-minutes.md
+++ b/_posts/2021-03-09-esc-minutes.md
@@ -27,12 +27,14 @@
### Gerrit events rewrite and GCloud pub/sub notifications
- Han-Wen has proposed [Change-Id: Ia54acb37](https://gerrit-review.googlesource.com/c/gerrit/+/296326)
- which represents the beginning of the initiative of having Gerrit
- notes exported as events. The
- [previous design in review posted by Alice](https://gerrit-review.googlesource.com/c/homepage/+/280925)
- has been abandoned because largely outdated compared to the current
- status on Gerrit master.
+Han-Wen has proposed [Change-Id: Ia54acb37](https://gerrit-review.googlesource.com/c/gerrit/+/296326)
+which represents the beginning of the initiative of having Gerrit
+events available over the REST API. The
+[previous design in review posted by Alice](https://gerrit-review.googlesource.com/c/homepage/+/280925)
+has been abandoned because largely outdated compared to the current
+status on Gerrit master.
+
+Luca and GerritForge will drive a redesign targeting Gerrit v3.5.
### Patch-set comment experiment in Gerrit v3.3
