host a git repo: change --bare to --mirror; rename (remove "style")

- plus some minor language fixes

Author: RubenKelevra

docs/how-to/host-git-style-repo.md docs/how-to/host-git-repo.mddocs/how-to/host-git-style-repo.md renamed to docs/how-to/host-git-repo.md

@@ -1,10 +1,10 @@
 ---
-title: Host a Git-style repo
+title: Host a Git repo
 legacyUrl: https://docs.ipfs.io/guides/examples/git/
-description: Learn how to serve a static Git repository worldwide using IPFS, the InterPlanetary File System.
+description: Learn how to serve a static Git repository worldwide using IPFS
 ---
 
-# Host a Git-style repo
+# Host a Git repo
 
 Have you ever said to yourself: "Man, my Git server isn't distributed enough" or "I wish I had an easy way to serve a static Git repository worldwide"? Well, wish no more.
 
@@ -13,7 +13,7 @@ In this guide, we discuss how to serve a Git repository through the IPFS network
 To start, select a Git repository you want to host, and do a bare clone of it:
 
 ```bash
-git clone --bare git@myhost.io/myrepo
+git clone --mirror git@myhost.io/myrepo
 ```
 
 For those who aren't super Git-savvy, a bare repository means that it doesn't have a working tree, and can be used as a server. They have a slightly different format than your normal Git repository.
@@ -56,7 +56,7 @@ $ git clone http://QmX679gmfyaRkKMvPA4WGNWXj9PtpvKWGPgtXaF18etC95.ipfs.localhost
 
 Note: make sure to change out that hash for yours.
 
-Now, you may be asking "Well, what good is a Git repository that I can't change anything on?" Here's one use case. Say you program in Go. For those who don't know, Go uses version control paths for its imports, i.e:
+Now, you may be asking, "Well, what good is a Git repository that I can't change anything on?" Here's one use case. Say you program in Go. For those who don't know, Go uses version control paths for its imports, i.e:
 
 ```go
 import (
@@ -78,3 +78,4 @@ import (
 And you will be guaranteed to have the same code every time!
 
 Note: Since Go doesn't allow the usage of localhost for import paths, we use the public HTTP gateways. This provides no security guarantees, as a man-in-the-middle attack could ship you bad code. You could use a domain name that redirects to the localhost instead to avoid the issue.
+