summaryrefslogtreecommitdiffstats
path: root/llvm/docs
diff options
context:
space:
mode:
authorLang Hames <lhames@gmail.com>2016-10-25 22:22:48 +0000
committerLang Hames <lhames@gmail.com>2016-10-25 22:22:48 +0000
commit6b19ce6adba80b13fc1ec456bd68c5b84f8eed44 (patch)
treea27143b7b0bb847ea16029ecc2408a8eeffb58e7 /llvm/docs
parentdff36738d1710288f7ab50460e5dc584be033951 (diff)
downloadbcm5719-llvm-6b19ce6adba80b13fc1ec456bd68c5b84f8eed44.tar.gz
bcm5719-llvm-6b19ce6adba80b13fc1ec456bd68c5b84f8eed44.zip
[docs] Fix a couple of typos in the new Error docs.
llvm-svn: 285133
Diffstat (limited to 'llvm/docs')
-rw-r--r--llvm/docs/ProgrammersManual.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/llvm/docs/ProgrammersManual.rst b/llvm/docs/ProgrammersManual.rst
index cc6d3f84d55..d970f1af04e 100644
--- a/llvm/docs/ProgrammersManual.rst
+++ b/llvm/docs/ProgrammersManual.rst
@@ -504,7 +504,7 @@ StringError
Many kinds of errors have no recovery strategy, the only action that can be
taken is to report them to the user so that the user can attempt to fix the
environment. In this case representing the error as a string makes perfect
-sense. LLVM provides the ``StringError class for this purpose. It takes two
+sense. LLVM provides the ``StringError`` class for this purpose. It takes two
arguments: A string error message, and an equivalent ``std::error_code`` for
interoperability:
@@ -582,7 +582,7 @@ Using ExitOnError to simplify tool code
"""""""""""""""""""""""""""""""""""""""
Library code should never call ``exit`` for a recoverable error, however in tool
-code (especially comamnd line tools) this can be a reasonable approach. Calling
+code (especially command line tools) this can be a reasonable approach. Calling
``exit`` upon encountering an error dramatically simplifies control flow as the
error no longer needs to be propagated up the stack. This allows code to be
written in straight-line style, as long as each fallible call is wrapped in a
OpenPOWER on IntegriCloud