Clarify the difference between googlesource.com and upstream Gerrit

Change-Id: I258a597e82dd60c4762b7270c1095d6f81fe8a02
diff --git a/pages/site/support.md b/pages/site/support.md
index 3d84936..9b85431 100644
--- a/pages/site/support.md
+++ b/pages/site/support.md
@@ -107,21 +107,24 @@
 
 The Gerrit team at Google runs its own Gerrit deployment under the
 `googlesource.com` domain. This deployment is in service of Google
-projects that have external visibility or external partners. As the
-deployment is based on the latest development release of Gerrit, this
-is where we focus our triage and support efforts. In particular:
+projects that have external visibility or external partners.  The
+deployment is based on the latest development commit of Gerrit.
 
-*  When filing a bug through the "report bug" link on
-   googlesource.com, we add `host-googlesource` label to filed
-   bugs. The frontend is shared between the googlesource and upstream
-   product, hence the frontend team at Google has a daily triage round to
-   look at all frontend/UI bugs
+Gerrit at `googlesource.com` shares its business logic with the
+publicly available gerrit code, but has important differences in
+low-level backend details, such as resource scaling, account handling,
+search index, and the git storage. It also lacks SSH support. Due to
+this we often lack expertise to analyze backend bugs on 'normal'
+gerrit installations.
 
-*  The backend team at Google has a daily triage for bugs with the
-   `googlesource` label. The Gerrit backend is very different between
-   googlesource and upstream flavors, so we do not have the expertise,
-   nor bandwidth to analyze functional bugs that do not reproduce on
-   `googlesource.com`.
+When filing a bug through the "report bug" link on googlesource.com,
+we add the `host-googlesource` label to filed bugs.
+
+*  The frontend team at Google has a daily triage round to look at all
+   frontend/UI bugs.
+
+*  The backend team does a daily triage on bugs that have the
+   `host-googlesource` label.
 
 *  We look at all security bugs as a matter of policy.