hmm, not sure about this note

I don’t want people to think it will be deprecated because I don’t
think it will. “rarely used” is probably better. It can be secured and
done over certs or basic auth, so I made that more general.

I people want to have a simple way to put static content up that’s
cloneable, it *can* sometimes be useful to use this protocol. I don’t
think that will change any time soon.

Author: schacon

book/11-git-internals/sections/transfer-protocols.asc

@@ -10,9 +10,9 @@ This protocol is called ``dumb'' because it requires no Git-specific code on the
 
 [NOTE]
 ====
-The dumb protocol is all but deprecated at this point.
-It's read-only to begin with, and not secure or private, so most Git hosts (both cloud-based and on-premises) will refuse to use it.
-It's advised to use the smart protocol, which we describe a bit further on.
+The dumb protocol is fairly rarely used these days.
+It's difficult to secure or make private, so most Git hosts (both cloud-based and on-premises) will refuse to use it.
+It's generally advised to use the smart protocol, which we describe a bit further on.
 ====
 
 Let's follow the `http-fetch` process for the simplegit library: