aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJim Laskey <jlaskey@mac.com>2006-07-31 20:18:49 +0000
committerJim Laskey <jlaskey@mac.com>2006-07-31 20:18:49 +0000
commitf55914a5292a0b163d4b05069b983da08c1e3f16 (patch)
treefe09af39806ce004ea39bf028b925f9930e90af3
parent6966c48767f988dec21598bdb0e551caad0dea7b (diff)
downloadexternal_llvm-f55914a5292a0b163d4b05069b983da08c1e3f16.zip
external_llvm-f55914a5292a0b163d4b05069b983da08c1e3f16.tar.gz
external_llvm-f55914a5292a0b163d4b05069b983da08c1e3f16.tar.bz2
Fix a couple typos.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@29416 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r--docs/CodingStandards.html2
-rw-r--r--docs/CommandLine.html2
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/CodingStandards.html b/docs/CodingStandards.html
index 36aced6..cec26fa 100644
--- 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 5898bb3..b04820e 100644
--- 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>