blog: add past season experience in GSoD 2020 post

content/blog/2019-09-26-september-19-dvc-heartbeat.md

@@ -59,7 +59,7 @@ Some other highlights of the end of summer:
   [DVC documentation](https://github.com/iterative/dvc.org) (and have something
   special in mind to celebrate our 100th contributors).
 
-- we enjoyed working with all the talented
+- We enjoyed working with all the talented
   [Google Season of docs](https://developers.google.com/season-of-docs/)
   applicants and now moving to the next stage with our chosen tech writer
   [Dashamir Hoxha](http://dashohoxha.fs.al/).

content/blog/2019-11-05-october-19-dvc-heartbeat.md

@@ -45,8 +45,8 @@ it this year. Here are some of the highlights:
   or
   [this tutorial in German](https://jupyter-tutorial.readthedocs.io/de/latest/reproduce/dvc/init.html)!
 
-- Having great time working with a [tech writer](https://github.com/dashohoxha)
-  brought to us by the
+- Having a great time working with a
+  [tech writer](https://github.com/dashohoxha) brought to us by the
   [Google Season of Docs](https://developers.google.com/season-of-docs) program.
   Check out these
   [interactive tutorials](https://dvc.org/doc/tutorials/interactive) we’ve

content/blog/2020-04-30-gsod-ideas-2020.md

@@ -21,14 +21,28 @@ tags:
 After a successful experience with **Google Season of Docs**
 [in 2019](/blog/dvc-project-ideas-for-google-summer-of-docs-2019), we're putting
 out a call for writers to apply to work with DVC as part of the
-[2020 edition](https://developers.google.com/season-of-docs). If you want to get
-involved with open source software documentation with mentorship from our team,
-read on.
+[2020 edition](https://developers.google.com/season-of-docs). If you want to
+write open source software documentation with mentorship from our team, read on.
 
-DVC has a dedicated docs team and a
+In last year's season, we partner with a [writer](https://github.com/dashohoxha)
+who helped us restructure important part of our docs, and address key issues.
+For example:
+
+- [Reorganize](https://github.com/iterative/dvc.org/pull/666) our tutorials
+- Build [interactive lessons](https://github.com/iterative/dvc.org/issues/546).
+  Check out our Tweet about it:
+
+  https://twitter.com/DVCorg/status/1205203662827483136
+
+- Docs [cleanup](https://github.com/iterative/dvc.org/pull/734)
+- Suggest creating a [How To](https://github.com/iterative/dvc.org/issues/563)
+  section of our docs
+- Other
+  [contributions](https://github.com/iterative/dvc.org/issues?q=is%3Aissue+dashohoxha+label%3Adoc-content)
+
+DVC now has a dedicated docs team and a
 [well-defined process](/doc/user-guide/contributing/docs) for creating and
-maintaining our documentation, while working closely with the core engineering
-team.
+maintaining our documentation, modeled in part based on this past experience.
 
 ## Prerequisites to apply