summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNico Weber <nicolasweber@gmx.de>2015-02-10 20:43:54 +0000
committerNico Weber <nicolasweber@gmx.de>2015-02-10 20:43:54 +0000
commit43f1836535b303193e47946f11ae7c4ac6b22798 (patch)
tree2e8f15fe1880aa961cb2739f1fc46cd7052c3386
parent9a18c3016cc4354093b66b1bb203f776910f976f (diff)
downloadbcm5719-llvm-43f1836535b303193e47946f11ae7c4ac6b22798.tar.gz
bcm5719-llvm-43f1836535b303193e47946f11ae7c4ac6b22798.zip
fix docs typo
llvm-svn: 228741
-rw-r--r--llvm/docs/ExceptionHandling.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/docs/ExceptionHandling.rst b/llvm/docs/ExceptionHandling.rst
index c8aa57cacc1..fe6876ad83a 100644
--- a/llvm/docs/ExceptionHandling.rst
+++ b/llvm/docs/ExceptionHandling.rst
@@ -328,7 +328,7 @@ C++ Exception Handling using the Windows Runtime
not yet fully implemented. The text below describes how it will work
when completed.)
-The Windows runtime function for C++ exception handling uses a mutli-phase
+The Windows runtime function for C++ exception handling uses a multi-phase
approach. When an exception occurs it searches the current callstack for a
frame that has a handler for the exception. If a handler is found, it then
calls the cleanup handler for each frame above the handler which has a
OpenPOWER on IntegriCloud