Makes more sense to refer to it as git.idk.i2p as well

i2p2www/pages/site/docs/applications/git.html

@@ -5,9 +5,7 @@
 {% block content %}
 <h1 id="git-over-i2p-for-users">Git over I2P for Users</h1>
 <p>{% trans -%} Tutorial for setting up git access through an I2P Tunnel. This tunnel will act as your access point to a single git service on I2P. {%- endtrans %}</p>
-<h2 id="before-anything-else-know-the-capabilities-the-service-offers-to-the-public">Before anything else: Know the capabilities the service offers to the public</h2>
-<p>{% trans -%} Depending on how the git service is configured, it may or may not offer all services on the same address. In the case of gittest.i2p, there is a public HTTP URL, but this URL is read-only and cannot be used to make changes. To do that, you must also know the SSH base32, which isn’t public at this time. Unless I’ve told you the SSH base32 to gittest.i2p, head over to the <a href="GITLAB.md">Server</a> tutorial to set up your own. {%- endtrans %}</p>
-<b>{% trans -%} If you intend to use the service at i2pgit.org, then you probably already have a tunnel configured and much of this
+<b>{% trans -%} If you intend to use the service at i2pgit.org/git.idk.i2p, then you probably already have a tunnel configured and much of this
 tutorial will not apply to you.{%- endtrans %}</b>
 <h2 id="first-set-up-an-account-at-a-git-service">First: Set up an account at a Git service</h2>
 <p>{% trans -%} To create your repositories on a remote git service, sign up for a user account at that service. Of course it’s also possible to create repositories locally and push them to a remote git service, but most will require an account and for you to create a space for the repository on the server. Gitlab has a very simple sign-up form: {%- endtrans %}</p>