krb5 commit: Remove some outdated iprop documentation

[Greg Hudson]

https://github.com/krb5/krb5/commit/16c3a5917a8fd2706a1e1b2e5a58e1319f8fa8f7
commit 16c3a5917a8fd2706a1e1b2e5a58e1319f8fa8f7
Author: Greg Hudson <ghudson at mit.edu>
Date:   Mon Sep 23 16:59:05 2019 -0400

    Remove some outdated iprop documentation
    
    Commit 969331732b62e73d1e073ff3ad87bf1774ee9fd1 (ticket 7369) removed
    the code to return UPDATE_BUSY if the database was modified within the
    last ten seconds, but did not remove the corresponding documentation
    text.  Remove it now.
    
    ticket: 8835 (new)
    tags: pullup
    target_version: 1.17-next

 doc/admin/database.rst |    8 +-------
 1 files changed, 1 insertions(+), 7 deletions(-)

diff --git a/doc/admin/database.rst b/doc/admin/database.rst
index 4b39b4d..6611f90 100644
--- a/doc/admin/database.rst
+++ b/doc/admin/database.rst
@@ -793,13 +793,7 @@ an "update log" file, maintained as a circular buffer of a certain
 size.  A process on each replica KDC connects to a service on the
 master KDC (currently implemented in the :ref:`kadmind(8)` server) and
 periodically requests the changes that have been made since the last
-check.  By default, this check is done every two minutes.  If the
-database has just been modified in the previous several seconds
-(currently the threshold is hard-coded at 10 seconds), the replica
-will not retrieve updates, but instead will pause and try again soon
-after.  This reduces the likelihood that incremental update queries
-will cause delays for an administrator trying to make a bunch of
-changes to the database at the same time.
+check.  By default, this check is done every two minutes.
 
 Incremental propagation uses the following entries in the per-realm
 data in the KDC config file (See :ref:`kdc.conf(5)`):