Fix a couple typos.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@29416 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/docs/CodingStandards.html b/docs/CodingStandards.html
index 36aced60a01c2ce3921ea924039ccb85ae903ecf..cec26fa67c6867dc30f2339e2d55ff7c8745dbb8 100644 (file)
--- a/docs/CodingStandards.html
+++ b/docs/CodingStandards.html
@@ -161,7 +161,7 @@ included, as well as any notes or "gotchas" in the code to watch out for.</p>
 
 <b>Class overviews</b>
 
-<p>Classes are one fundemental part of a good object oriented design.  As such,
+<p>Classes are one fundamental part of a good object oriented design.  As such,
 a class definition should have a comment block that explains what the class is
 used for... if it's not obvious.  If it's so completely obvious your grandma
 could figure it out, it's probably safe to leave it out.  Naming classes

diff --git a/docs/CommandLine.html b/docs/CommandLine.html
index 5898bb31137e71605110e0519a5e3980a2029c16..b04820e88a5a08ae35f895cc765a4ad8aa3540d6 100644 (file)
--- a/docs/CommandLine.html
+++ b/docs/CommandLine.html
@@ -1763,7 +1763,7 @@ your custom data type.<p>
 <p>This approach has the advantage that users of your custom data type will
 automatically use your custom parser whenever they define an option with a value
 type of your data type.  The disadvantage of this approach is that it doesn't
-work if your fundemental data type is something that is already supported.</p>
+work if your fundamental data type is something that is already supported.</p>
 
 </li>