r201713 - Some of these headings had the incorrect number of "underlines" and so would get warnings when generating the content from Sphinx. No functional changes intended.

[Aaron Ballman]

Author: aaronballman
Date: Wed Feb 19 14:43:58 2014
New Revision: 201713

URL: http://llvm.org/viewvc/llvm-project?rev=201713&view=rev
Log:
Some of these headings had the incorrect number of "underlines" and so would get warnings when generating the content from Sphinx. No functional changes intended.

Modified:
    cfe/trunk/docs/ThreadSafetyAnalysis.rst

Modified: cfe/trunk/docs/ThreadSafetyAnalysis.rst
URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/docs/ThreadSafetyAnalysis.rst?rev=201713&r1=201712&r2=201713&view=diff
==============================================================================
--- cfe/trunk/docs/ThreadSafetyAnalysis.rst (original)
+++ cfe/trunk/docs/ThreadSafetyAnalysis.rst Wed Feb 19 14:43:58 2014
@@ -80,7 +80,7 @@ as such (using ``LOCK``/``UNLOCK_FUNCTIO
 
 
 Running The Analysis
----------------------
+--------------------
 
 To run the analysis, simply compile with the ``-Wthread-safety`` flag, e.g.
 
@@ -388,7 +388,7 @@ as ``(UN)LOCK_FUNCTION``.  See :ref:`mut
 
 
 ASSERT_EXCLUSIVE_LOCK(...) and ASSERT_SHARED_LOCK(...)
---------------------------------------------------
+------------------------------------------------------
 
 These are attributes on a function or method that does a run-time test to see
 whether the calling thread holds the given capability.  The function is assumed
@@ -437,7 +437,7 @@ Frequently Asked Questions
 .. _limitations:
 
 Known Limitations 
-==================
+=================
 
 Lexical scope
 -------------