Improve submodule config, minor README updates

 * In response to issue 5 [1] I've changed the git submodule config to
   references GitHub using HTTPS instead of the git protocol, this
   should make it easier for people behind firewalls to clone the
   repository.

 * In response to an issue [2] reported against one of my other Vim
   plug-ins I've changed the link to the ZIP archive to include the
   ".zip" extension. The old links without extensions will keep working
   so as not to break links in older README files.

 * The link with the text "CTRL-]" broke some Markdown implementations
   so I changed the text to use an HTML entity instead of a plain "]".

[1] https://github.com/xolox/vim-easytags/issues/5
[2] https://github.com/xolox/vim-session/issues/5

3 files changed, 5 insertions, 5 deletions

diff --git a/.gitmodules b/.gitmodules
index c98216e..5498be8 100644
--- a/.gitmodules
+++ b/.gitmodules
@@ -1,3 +1,3 @@
 [submodule "autoload/xolox/misc"]
 	path = autoload/xolox/misc
-	url = git://github.com/xolox/vim-misc.git
+	url = https://github.com/xolox/vim-misc.git
diff --git a/README.md b/README.md
index 4860c63..6d42350 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
 # Automated tag generation and syntax highlighting in Vim
 
-[Vim](http://www.vim.org/) has long been my favorite text editor and combined with [Exuberant Ctags] [exuberant_ctags] it has the potential to provide most of what I expect from an [integrated development environment](http://en.wikipedia.org/wiki/Integrated_development_environment). Exuberant Ctags is the latest incarnation of a [family of computer programs](http://en.wikipedia.org/wiki/Ctags) that scan source code files to create an index of identifiers (tags) and where they are defined. Vim uses this index (a so-called tags file) to enable you to jump to the definition of any identifier using the [Control-\]](http://vimdoc.sourceforge.net/htmldoc/tagsrch.html#CTRL-]) mapping.
+[Vim](http://www.vim.org/) has long been my favorite text editor and combined with [Exuberant Ctags] [exuberant_ctags] it has the potential to provide most of what I expect from an [integrated development environment](http://en.wikipedia.org/wiki/Integrated_development_environment). Exuberant Ctags is the latest incarnation of a [family of computer programs](http://en.wikipedia.org/wiki/Ctags) that scan source code files to create an index of identifiers (tags) and where they are defined. Vim uses this index (a so-called tags file) to enable you to jump to the definition of any identifier using the [Control-]](http://vimdoc.sourceforge.net/htmldoc/tagsrch.html#CTRL-]) mapping.
 
 When you're familiar with integrated development environments you may recognize this feature as "Go-to definition". One advantage of the combination of Vim and Exuberant Ctags over integrated development environments is that Vim supports syntax highlighting for [over 500 file types](http://ftp.vim.org/vim/runtime/syntax/) (!) and Exuberant Ctags can generate tags for [over 40 file types](http://ctags.sourceforge.net/languages.html) as well...
 
@@ -8,7 +8,7 @@ There's just one problem: You have to manually keep your tags files up-to-date a
 
 ## Install & usage
 
-Unzip the most recent [ZIP archive](http://peterodding.com/code/vim/downloads/easytags) file inside your Vim profile directory (usually this is `~/.vim` on UNIX and `%USERPROFILE%\vimfiles` on Windows), restart Vim and execute the command `:helptags ~/.vim/doc` (use `:helptags ~\vimfiles\doc` instead on Windows). Now try it out: Edit any file type supported by Exuberant Ctags and within ten seconds the plug-in should create/update your tags file (`~/.vimtags` on UNIX, `~/_vimtags` on Windows) with the tags defined in the file you just edited! This means that whatever file you're editing in Vim (as long as it's on the local file system), tags will always be available by the time you need them!
+Unzip the most recent [ZIP archive](http://peterodding.com/code/vim/downloads/easytags.zip) file inside your Vim profile directory (usually this is `~/.vim` on UNIX and `%USERPROFILE%\vimfiles` on Windows), restart Vim and execute the command `:helptags ~/.vim/doc` (use `:helptags ~\vimfiles\doc` instead on Windows). Now try it out: Edit any file type supported by Exuberant Ctags and within ten seconds the plug-in should create/update your tags file (`~/.vimtags` on UNIX, `~/_vimtags` on Windows) with the tags defined in the file you just edited! This means that whatever file you're editing in Vim (as long as it's on the local file system), tags will always be available by the time you need them!
 
 Additionally if the file you just opened is a C, C++, Objective-C, Java, Lua, Python, PHP or Vim source file you should also notice that the function and type names defined in the file have been syntax highlighted.
 
diff --git a/doc/easytags.txt b/doc/easytags.txt
index 4523cca..3694620 100644
--- a/doc/easytags.txt
+++ b/doc/easytags.txt
@@ -361,7 +361,7 @@ References ~
 [3] http://en.wikipedia.org/wiki/Ctags
 [4] http://ftp.vim.org/vim/runtime/syntax/
 [5] http://ctags.sourceforge.net/languages.html
-[6] http://peterodding.com/code/vim/downloads/easytags
+[6] http://peterodding.com/code/vim/downloads/easytags.zip
 [7] http://peterodding.com/code/vim/shell/
 [8] http://en.wikipedia.org/wiki/Dynamic-link_library
 [9] http://en.wikipedia.org/wiki/Symbolic_link
@@ -371,4 +371,4 @@ References ~
 [13] http://www.vim.org/scripts/script.php?script_id=3114
 [14] http://en.wikipedia.org/wiki/MIT_License
 
-vim: syntax=help nospell
\ No newline at end of file
+vim: syntax=help nospell