Remove references to removed FTP function

This fixes #912

docs/zdgbook/Outline.txt

@@ -46,7 +46,7 @@ designed to be used and managed through a network interface, most
 commonly HTTP.
 
 Zope provides network access to components by "publishing" them
-through various network interfaces like HTTP, FTP, WebDAV and
+through various network interfaces like HTTP, WebDAV and
 XML-RPC.  This chapter describes how a component developer can
 publish their components "through the web" and other network
 protocols.

docs/zdgbook/Products.rst

@@ -244,8 +244,8 @@ OFS.SimpleItem.Item
 This base class provides your product with the basics needed to work
 with the Zope management interface.  By inheriting from ``Item`` your
 product class gains a whole host of features: the ability to be cut
-and pasted, capability with management views, WebDAV support, basic
-FTP support, undo support, ownership support, and traversal controls.
+and pasted, capability with management views, WebDAV support,
+undo support, ownership support, and traversal controls.
 It also gives you some standard methods for management views and
 error display including ``manage_main()``.  You also get the
 ``getId()``, ``title_or_id()``, ``title_and_id()`` methods and the
@@ -309,7 +309,7 @@ This base class gives your product the ability to contain other
 ``Item`` instances.  In other words, it makes your product class like
 a Zope folder.  This base class is optional. See the *API Reference*
 for more details.  This base class gives you facilities for adding
-Zope objects, importing and exporting Zope objects, WebDAV, and FTP.
+Zope objects, importing and exporting Zope objects and WebDAV.
 It also gives you the ``objectIds``, ``objectValues``, and
 ``objectItems`` methods.
 
@@ -1088,21 +1088,20 @@ In addition to providing a through the web management interface your
 products may also support many other user interfaces.  You product
 might have no web management interfaces, and might be controlled
 completely through some other network protocol.  Zope provides
-interfaces and support for FTP, WebDAV and XML-RPC.  If this isn't
+interfaces and support for WebDAV and XML-RPC.  If this isn't
 enough you can add other protocols.
 
-FTP and WebDAV Interfaces
--------------------------
+WebDAV Interfaces
+-----------------
 
-Both FTP and WebDAV treat Zope objects like files and
-directories.  See Chapter 3 for more information on FTP and WebDAV.
+WebDAV treats Zope objects like files and
+directories.  See Chapter 3 for more information on WebDAV.
 
 By simply sub-classing from 'SimpleItem.Item' and 'ObjectManager' if
-necessary, you gain basic FTP and WebDAV support.  Without any work
-your objects will appear in FTP directory listings and if your class
-is an 'ObjectManager' its contents will be accessible via FTP and
-WebDAV.  See Chapter 2 for more information on implementing FTP and
-WebDAV support.
+necessary, you gain basic WebDAV support.  Without any work
+your objects will appear in directory listings and if your class
+is an 'ObjectManager' its contents will be accessible via WebDAV.
+See Chapter 2 for more information on implementing WebDAV support.
 
 XML-RPC and Network Services
 ----------------------------

docs/zdgbook/Security.rst

@@ -32,7 +32,7 @@ system.
 How The Security Policy Relates to Zope's Publishing Machinery
 --------------------------------------------------------------
 
-When access to Zope is performed via HTTP, WebDAV, or FTP, Zope's
+When access to Zope is performed via HTTP or WebDAV, Zope's
 publishing machinery consults the security policy in order to
 determine whether to allow or deny access to a visitor for a
 particular object.  For example, when a user visits the root
@@ -52,7 +52,7 @@ How The Security Policy Relates to Restricted Code
 --------------------------------------------------
 
 *Restricted code* is generally any sort of logic that may be edited
-remotely (through the Web, FTP, via WebDAV or by other means). DTML
+remotely (through the Web, via WebDAV or by other means). DTML
 Methods, SQLMethods, Python Scripts and Page Templates are examples of
 restricted code.
 
@@ -304,7 +304,7 @@ When Should I Use Security Assertions?
 
 If you are building an object that will be used from a Page Template or
 other restricted code, or that will be accessible directly through the web
-(or other remote protocols such as FTP or WebDAV) then you need to
+(or other remote protocols such as WebDAV) then you need to
 define security information for your object.