README.md: Move 'Talks' back into 'Intorudction'

[code/vcsh.git] / README.md

diff --git a/README.md b/README.md
index fecaaf4fc5cfff3b4b923991019f0106df4ce8a9..4ecb54fc0df160225156fa6b2105d3e863bbee76 100644 (file)
--- a/README.md
+++ b/README.md
@@ -36,6 +36,12 @@ does not read `INSTALL.md` for install instructions or `PACKAGING.md` to create
 a package, yourself. If you do end up packaging `vcsh` please let us know so we
 can give you your own packaging branch in the upstream repository.
 
+## Talks ##
+
+Some people found it useful to look at slides and videos explaining how `vcsh`
+works instead of working through the docs, first.
+They can all be found [on the author's talk page][talks].
+
 
 # 30 second howto #
 
@@ -49,23 +55,12 @@ Let's say you want to version control your `vim` configuration:
     vcsh vim add ~/.vimrc ~/.vim
     vcsh vim commit -m 'Initial commit of my Vim configuration'
     # optionally push your files to a remote
-    vcsh vim remote add origin REMOTE
+    vcsh vim <remote> add origin REMOTE
     vcsh vim push origin master:master
 
 If all that looks a _lot_ like standard `git`, that's no coincidence; it's
 a design feature.
 
-Once you get familiar with `vcsh`, it's strongly suggested that you look
-into more advanced usage scenarios, especially on how to manage your
-`vcsh` and other repositories with [mr][mr].
-
-
-## Talks ##
-
-Some people found it useful to look at slides and videos explaining how `vcsh`
-works instead of working through the docs, first.
-They can all be found [on the author's talk page][talks].
-
 
 # Overview