@@ -369,8 +369,8 @@ WARN::function declared to return type EMP does not retrieve (EMP.*)
369369 has the same name as the C source function the first form of the
370370 statement is used. The string argument in the AS clause is the
371371 full pathname of the file that contains the dynamically loadable
372- compiled object. If the name of C function is different from the
373- name of the SQL function, then the second form is used. In this
372+ compiled object. If the name ofthe C function is different from the
373+ desired name of the SQL function, then the second form is used. In this
374374 form the AS clause takes two string arguments, the first is the
375375 full pathname of the dynamically loadable object file, and the
376376 second is the link symbol that the dynamic loader should search
@@ -392,7 +392,7 @@ WARN::function declared to return type EMP does not retrieve (EMP.*)
392392 code file for the function, bracketed by quotation marks. If a
393393 link symbol is used in the AS clause, the link symbol should also be
394394 bracketed by single quotation marks, and should be exactly the
395- same as the name of function in the C source code. On UNIX systems
395+ same as the name ofthe function in the C source code. On UNIX systems
396396 the command <command>nm</command> will print all of the link
397397 symbols in a dynamically loadable object.
398398 (<productname>Postgres</productname> will not compile a function
@@ -991,7 +991,7 @@ memmove(destination->data, buffer, 40);
991991 </para>
992992
993993 <sect3>
994- <title>Pre-v6.5 </title>
994+ <title>Pre-v6.6 </title>
995995
996996 <para>
997997 For functions written in C, the SQL name declared in
@@ -1029,7 +1029,9 @@ memmove(destination->data, buffer, 40);
10291029 they can be declared with the same SQL names (as long as their
10301030 argument types differ, of course). This way avoids the overhead of
10311031 an SQL wrapper function, at the cost of more effort to prepare a
1032- custom backend executable.
1032+ custom backend executable. (This option is only available in version
1033+ 6.5 and later, since prior versions required internal functions to
1034+ have the same name in SQL as in the C code.)
10331035 </para>
10341036 </sect3>
10351037 </sect2>