[llvm-branch-commits] [clang] b65707e - [ReleaseNotes] Fix typos

[Sven van Haastregt via llvm-branch-commits]

Author: Sven van Haastregt
Date: 2020-02-27T14:42:46Z
New Revision: b65707e4818e3b5694786b90e6ebdaa17910b016

URL: https://github.com/llvm/llvm-project/commit/b65707e4818e3b5694786b90e6ebdaa17910b016
DIFF: https://github.com/llvm/llvm-project/commit/b65707e4818e3b5694786b90e6ebdaa17910b016.diff

LOG: [ReleaseNotes] Fix typos

Added: 
    

Modified: 
    clang/docs/ReleaseNotes.rst

Removed: 
    


################################################################################
diff  --git a/clang/docs/ReleaseNotes.rst b/clang/docs/ReleaseNotes.rst
index d959791d75b6..c3097bcba8dc 100644
--- a/clang/docs/ReleaseNotes.rst
+++ b/clang/docs/ReleaseNotes.rst
@@ -292,7 +292,7 @@ Objective-C Language Changes in Clang
 
   One particular issue you may run into is attempting to use a class
   as a key in a dictionary literal. This will now result in an error,
-  because ``Class`` is not convertable to ``id<NSCopying>``. (Note that
+  because ``Class`` is not convertible to ``id<NSCopying>``. (Note that
   this was already a warning in Objective-C mode.) While an arbitrary
   ``Class`` object is not guaranteed to implement ``NSCopying``, the
   default metaclass implementation does. Therefore, the recommended
@@ -500,7 +500,7 @@ Static Analyzer
 
 - ``deadcode.DeadStores`` now warns about nested dead stores.
 
-- Condition values that are relevant to the occurance of a bug are far better
+- Condition values that are relevant to the occurrence of a bug are far better
   explained in bug reports.
 
 - Despite still being at an alpha stage, checkers implementing taint analyses