From: W. Trevor King Date: Sun, 10 Feb 2013 15:10:37 GMT Subject: [PATCH v2 11/15] user-manual: Fix 'http' -> 'HTTP' typos Message-ID: <9a46edb449eed4834336887e1827749767a69cb1.1360508415.git.wking@tremily.us> In-Reply-To: From: "W. Trevor King" HTTP is an acronym which has not (yet) made the transition to word status (unlike "laser", probably because lasers are inherently cooler than HTTP ;). Signed-off-by: W. Trevor King --- Documentation/user-manual.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index 07e07c1..31054a2 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt @@ -1938,7 +1938,7 @@ Exporting a Git repository via http ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Git protocol gives better performance and reliability, but on a -host with a web server set up, http exports may be simpler to set up. +host with a web server set up, HTTP exports may be simpler to set up. All you need to do is place the newly created bare Git repository in a directory that is exported by the web server, and make some @@ -1964,7 +1964,7 @@ $ git clone http://yourserver.com/~you/proj.git (See also link:howto/setup-git-server-over-http.txt[setup-git-server-over-http] for a slightly more sophisticated setup using WebDAV which also -allows pushing over http.) +allows pushing over HTTP.) [[pushing-changes-to-a-public-repository]] Pushing changes to a public repository -- 1.8.1.336.g94702dd