[llvm] r285141 - [docs] Avoid repetition of 'considerable' in Error docs.

[Lang Hames via llvm-commits]

Author: lhames
Date: Tue Oct 25 18:08:32 2016
New Revision: 285141

URL: http://llvm.org/viewvc/llvm-project?rev=285141&view=rev
Log:
[docs] Avoid repetition of 'considerable' in Error docs.

Modified:
    llvm/trunk/docs/ProgrammersManual.rst

Modified: llvm/trunk/docs/ProgrammersManual.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/ProgrammersManual.rst?rev=285141&r1=285140&r2=285141&view=diff
==============================================================================
--- llvm/trunk/docs/ProgrammersManual.rst (original)
+++ llvm/trunk/docs/ProgrammersManual.rst Tue Oct 25 18:08:32 2016
@@ -738,16 +738,16 @@ Building fallible iterators and iterator
 
 The archive walking examples above retrieve archive members by index, however
 this requires considerable boiler-plate for iteration and error checking. We can
-clean this up considerably by using ``Error`` with the "fallible iterator"
-pattern. The usual C++ iterator patterns do not allow for failure on increment,
-but we can incorporate support for it by having iterators hold an Error
-reference through which they can report failure. In this pattern, if an
-increment operation fails the failure is recorded via the Error reference and
-the iterator value is set to the end of the range in order to terminate the
-loop. This ensures that the dereference operation is safe anywhere that an
-ordinary iterator dereference would be safe (i.e. when the iterator is not equal
-to end). Where this pattern is followed (as in the ``llvm::object::Archive``
-class) the result is much cleaner iteration idiom:
+clean this up by using ``Error`` with the "fallible iterator" pattern. The usual
+C++ iterator patterns do not allow for failure on increment, but we can
+incorporate support for it by having iterators hold an Error reference through
+which they can report failure. In this pattern, if an increment operation fails
+the failure is recorded via the Error reference and the iterator value is set to
+the end of the range in order to terminate the loop. This ensures that the
+dereference operation is safe anywhere that an ordinary iterator dereference
+would be safe (i.e. when the iterator is not equal to end). Where this pattern
+is followed (as in the ``llvm::object::Archive`` class) the result is much
+cleaner iteration idiom:
 
 .. code-block:: c++