Fix spelling of 'separate'.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@23971 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Jeff Cohen 2005-10-24 16:54:55 +00:00
parent cb9b4f9c14
commit 0b81cdae50
2 changed files with 3 additions and 3 deletions

View File

@ -1117,7 +1117,7 @@ converted to a list of <a href="#machineinstr">MachineInstr</a>s and the
Selection DAG is destroyed.
</p>
<p>Note that this phase is logically seperate from the instruction selection
<p>Note that this phase is logically separate from the instruction selection
phase, but is tied to it closely in the code because it operates on
SelectionDAGs.</p>

View File

@ -337,7 +337,7 @@ for different types. These rules allow you to assign a value like "7" to a
information that TableGen collects. Records are defined with a <tt>def</tt> or
<tt>class</tt> keyword, the record name, and an optional list of "<a
href="#templateargs">template arguments</a>". If the record has superclasses,
they are specified as a comma seperated list that starts with a colon character
they are specified as a comma separated list that starts with a colon character
(":"). If <a href="#valuedef">value definitions</a> or <a href="#recordlet">let
expressions</a> are needed for the class, they are enclosed in curly braces
("{}"); otherwise, the record ends with a semicolon. Here is a simple TableGen
@ -517,7 +517,7 @@ multiple records at a time, and may be useful in certain other cases.
File-scope let expressions are really just another way that TableGen allows the
end-user to factor out commonality from the records.</p>
<p>File-scope "let" expressions take a comma-seperated list of bindings to
<p>File-scope "let" expressions take a comma-separated list of bindings to
apply, and one of more records to bind the values in. Here are some
examples:</p>