Update Using a Geo Server

- Removed secondary steps
- Added push to secondary git output example

doc/administration/geo/replication/using_a_geo_server.md

@@ -2,21 +2,17 @@
 
 # Using a Geo Server
 
-After you set up the [database replication and configure the Geo nodes][req],
-there are a few things to consider:
+After you set up the [database replication and configure the Geo nodes][req], use your closest GitLab node as you would a normal standalone GitLab instance.
 
-Users need an extra step to be able to fetch code from the secondary and push to primary:
+Pushing directly to a **secondary** node (for both HTTP, SSH including git-lfs) was [introduced](https://about.gitlab.com/2018/09/22/gitlab-11-3-released/) in [GitLab Premium](https://about.gitlab.com/pricing/#self-managed) 11.3.
 
-1. Clone the repository as you would normally do, but from the secondary node:
+Example of the output you will see when pushing to a **secondary** node:
 
-  ```bash
-  git clone git@secondary.gitlab.example.com:user/repo.git
-  ```
-
-1. Change the remote push URL to always push to primary, following this example:
-
-  ```bash
-  git remote set-url --push origin git@primary.gitlab.example.com:user/repo.git
-  ```
+```bash
+$ git push
+> GitLab: You're pushing to a Geo secondary.
+> GitLab: We'll help you by proxying this request to the primary: ssh://git@primary.geo/user/repo.git
+Everything up-to-date
+```
 
 [req]: index.md#setup-instructions