r176948 - Documentation: formatting fixes

[Dmitri Gribenko]

Author: gribozavr
Date: Wed Mar 13 09:26:35 2013
New Revision: 176948

URL: http://llvm.org/viewvc/llvm-project?rev=176948&view=rev
Log:
Documentation: formatting fixes

Modified:
    cfe/trunk/docs/AutomaticReferenceCounting.rst

Modified: cfe/trunk/docs/AutomaticReferenceCounting.rst
URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/docs/AutomaticReferenceCounting.rst?rev=176948&r1=176947&r2=176948&view=diff
==============================================================================
--- cfe/trunk/docs/AutomaticReferenceCounting.rst (original)
+++ cfe/trunk/docs/AutomaticReferenceCounting.rst Wed Mar 13 09:26:35 2013
@@ -1347,7 +1347,7 @@ object pointer.  The corresponding actua
 However, under certain circumstances, ARC is permitted to re-order and
 eliminate operations in a manner which may alter the overall
 computation history beyond what is permitted by the general "as if"
-rule of C/C++ and the :ref:`restrictions <_arc.objects.retains>` on
+rule of C/C++ and the :ref:`restrictions <arc.objects.retains>` on
 the implementation of ``retain`` and ``release``.
 
 .. admonition:: Rationale
@@ -1359,6 +1359,7 @@ the implementation of ``retain`` and ``r
   example, consider the following code:
 
   .. code-block:: objc
+
     id x = _ivar;
     [x foo];
 
@@ -1450,7 +1451,7 @@ dependency is not carried by values that
   itself cause dependence, but since generally the optimizer will not
   be able to prove that the function doesn't depend on that parameter,
   it will be forced to conservatively assume it does.
-  
+
   Dependency propagates to values loaded from a pointer because those
   values might be invalidated by deallocating the object.  For
   example, given the code ``__strong id x = p->ivar;``, ARC must not