From 120bc6da2fe9b6706de2f5ee890a844cb91ae2d5 Mon Sep 17 00:00:00 2001
From: Chris Lattner <sabre@nondot.org>
Date: Sat, 14 May 2005 01:30:15 +0000
Subject: [PATCH] minor changes

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@21998 91177308-0d34-0410-b5e6-96231b3b80d8
---
 docs/BytecodeFormat.html | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

diff --git a/docs/BytecodeFormat.html b/docs/BytecodeFormat.html
index 0e36db2eb4b..dd395306611 100644
--- a/docs/BytecodeFormat.html
+++ b/docs/BytecodeFormat.html
@@ -1624,19 +1624,18 @@ In each of these entries in range 56-63, the opcode is documented as the base
 opcode (Invoke, Call, Store) plus some set of modifiers, as follows:</p>
 <dl>
   <dt>CC</dt>
-  <dd>This means a generic (user defined) calling convention number is specified
-  in a VBR that follows the opcode immediately. This is used when the calling 
-  convention for the Invoke or the Call instruction is not one of the LLVM 
-  standard ones (like FastCC or CCC)
+  <dd>This means an arbitrary calling convention is specified
+  in a VBR that follows the opcode. This is used when the instruction cannot
+  be encoded with one of the more compact forms.
   </dd>
   <dt>FastCC</dt>
   <dd>This indicates that the Call or Invoke is using the FastCC calling 
-  convention which puts arguments in registers to avoid stack loading.</dd>
+  convention.</dd>
   <dt>CCC</dt>
-  <dd>This indicates that the Call or Invoke is using the "C" calling convention
-  which is specified by the C99 language.</dd>
+  <dd>This indicates that the Call or Invoke is using the native "C" calling 
+  convention.</dd>
   <dt>TailCall</dt>
-  <dd>This indicates that the Call or Invoke is a tail call.</dd>
+  <dd>This indicates that the Call has the 'tail' modifier.</dd>
 </dl>
 
 <!-- _______________________________________________________________________ -->