Clarify secondary proxy accelerated features docs

Explicitly mention all writes are proxied and flip the table from
proxied, to accelerated.

doc/administration/geo/secondary_proxy/index.md

@@ -102,25 +102,25 @@ for progress.
 ## Features accelerated by secondary Geo sites
 
 Most HTTP traffic sent to a secondary Geo site can be proxied to the primary Geo site. With this architecture,
-secondary Geo sites are able to support write requests. Certain requests are handled locally by secondary
-sites for improved latency and bandwidth nearby.
+secondary Geo sites are able to support write requests. Certain **read** requests are handled locally by secondary
+sites for improved latency and bandwidth nearby. All write requests are proxied to the primary site.
 
 The following table details the components currently tested through the Geo secondary site Workhorse proxy.
 It does not cover all data types, more will be added in the future as they are tested.
 
-| Feature / component                                 | Proxied?               |
+| Feature / component                                 | Accelerated reads?     |
 |:----------------------------------------------------|:-----------------------|
-| Project, wiki, design repository (using the web UI) | **{check-circle}** Yes |
-| Project, wiki repository (using Git)                | **{dotted-circle}** Partly <sup>1</sup> |
-| Project, Personal Snippet (using the web UI)        | **{check-circle}** Yes |
-| Project, Personal Snippet (using Git)               | **{dotted-circle}** Partly <sup>1</sup> |
-| Group wiki repository (using the web UI)            | **{check-circle}** Yes |
-| Group wiki repository (using Git)                   | **{dotted-circle}** Partly <sup>1</sup> |
-| User uploads                                        | **{check-circle}** Yes |
-| LFS objects (using the web UI)                      | **{check-circle}** Yes |
+| Project, wiki, design repository (using the web UI) | **{dotted-circle}** No |
+| Project, wiki repository (using Git)                | **{check-circle}** Yes <sup>1</sup> |
+| Project, Personal Snippet (using the web UI)        | **{dotted-circle}** No |
+| Project, Personal Snippet (using Git)               | **{check-circle}** Yes <sup>1</sup> |
+| Group wiki repository (using the web UI)            | **{dotted-circle}** No |
+| Group wiki repository (using Git)                   | **{check-circle}** Yes <sup>1</sup> |
+| User uploads                                        | **{dotted-circle}** No |
+| LFS objects (using the web UI)                      | **{dotted-circle}** No |
 | LFS objects (using Git)                             | **{check-circle}** Yes |
 | Pages                                               | **{dotted-circle}** No <sup>2</sup> |
-| Advanced search (using the web UI)                  | **{check-circle}** Yes |
+| Advanced search (using the web UI)                  | **{dotted-circle}** No |
 
 1. Git reads are served from the local secondary while pushes get proxied to the primary.
    Selective sync or cases where repositories don't exist locally on the Geo secondary throw a "not found" error.