updates for web remote and removing URL backend

2 files changed, 1 insertions, 25 deletions

diff --git a/doc/walkthrough/using_the_SHA1_backend.mdwn b/doc/walkthrough/using_the_SHA1_backend.mdwn
index c04729e2c..70dc2ef75 100644
--- a/doc/walkthrough/using_the_SHA1_backend.mdwn
+++ b/doc/walkthrough/using_the_SHA1_backend.mdwn
@@ -1,4 +1,4 @@
-Another handy alternative to the default [[backend|backends]] is the
+A handy alternative to the default [[backend|backends]] is the
 SHA1 backend. This backend provides more git-style assurance that your data
 has not been damaged. And the checksum means that when you add the same
 content to the annex twice, only one copy need be stored in the backend.
diff --git a/doc/walkthrough/using_the_URL_backend.mdwn b/doc/walkthrough/using_the_URL_backend.mdwn
deleted file mode 100644
index 50da4dad8..000000000
--- a/doc/walkthrough/using_the_URL_backend.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-git-annex has multiple key-value [[backends]]. So far you have been using
-the default, WORM (Write Once, Read Many) backend.
-
-Another handy backend is the URL backend, which can fetch file's content
-from remote URLs. Here's how to set up some files in your repository
-that use this backend:
-
-	# git annex fromkey --key=URL--http://www.archive.org/somefile somefile
-	fromkey somefile ok
-	# git commit -m "added a file from the Internet Archive"
-
-Now you if you ask git-annex to get that file, it will download it, 
-and cache it locally.
-
-	# git annex get somefile
-	get somefile (downloading)
-	#########################################################################100.0%
-	ok
-
-You can always drop files downloaded by the URL backend. It is assumed
-that the URL is stable; no local backup is kept.
-
-	# git annex drop somefile
-	drop somefile (ok)