Changed Ownership tab. Got rid of implicit/explicit ownership. Now yo…

…u just choose to take ownership of subobjects (or not) when taking ownership.

help/Ownership.stx

@@ -26,41 +26,21 @@ Ownership: Manage ownership.
     are *unowned*. An unowned executable object executes with the
     permissions of the user running the object.
 
-    There are three possible states of ownership that a Zope object
-    may be in. The object may be *unowned*, it may be *owned directly*
-    or it may be *owned implicitly*.  If an object is owned directly,
-    the ownership information is stored in the object itself. If an
-    object is owned implicitly, it acquires its ownership information
-    from its container (which may in turn acquire its ownership
-    information from its container, and so on).
-
-    When Zope automatically assigns ownership to newly created or
-    copied objects, it tries to use implicit ownership if
-    possible. This makes it easier to change the ownership of many
-    objects at one time without having to visit each object
-    directly. For example, if everything in the folder 'research' is
-    owned by Fred and you want to change the ownership of everything
-    in the folder to Jim, you only need to visit the 'research' folder
-    and change the ownership there if all of the objects under
-    'research' are owned implicitly.
-
     It is possible to remove a user in your Zope installation while
     objects that were owned by that user remain (for instance, someone
     in your organization moves on, so you remove his account on your
     Zope server). When you remove a Zope user, objects that were owned
     by that user still have ownership information that refers to that
     user. This will not cause an error, but it is important to
     understand what happens to Zope objects whose owners no longer
-    exist.
-
-    This is most important for "executable" objects. Usually, the
-    abilities of executable objects are constrained by the abilities
-    of the object's owner as well as the user causing the object to
-    execute. If Zope cannot find the user that the executable's
-    ownership information refers to when it tries to execute the
-    object, it will use the special 'nobody' or anonymous user
-    instead. The 'nobody' user has very minimal privileges, so you
-    should take this into account when deciding what to do about a
+    exist.  This is most important for "executable" objects. Usually,
+    the abilities of executable objects are constrained by the
+    abilities of the object's owner as well as the user causing the
+    object to execute. If Zope cannot find the user that the
+    executable's ownership information refers to when it tries to
+    execute the object, it will use the special 'nobody' or anonymous
+    user instead. The 'nobody' user has very minimal privileges, so
+    you should take this into account when deciding what to do about a
     user's owned objects when you delete the user. If the user had
     DTML documents or other executable objects that depended upon
     their owner to have a higher level of privilege than the 'nobody'
@@ -73,14 +53,6 @@ Ownership: Manage ownership.
 
       **Note: For this operation you have the 'Take ownership' role.**
 
-    'Make ownership implicit (acquired)' -- Remove ownership
-    information for this object so that it is acquired from its
-    container.
-
-      **Note: This operation will fail if it would result in a change
-      of ownership.**
-
-    'Make ownership explicit' -- Add ownership information to this
-    object.
+    'Also take ownership of all sub-objects' -- Gives you ownership of all the current object's sub-objects when you take ownership of the current object. Normally you should leave this option checked.