@@ -294,35 +294,6 @@ SELECT 'fat cats ate fat rats'::tsvector @@ to_tsquery('fat & rat');
294294 already normalized, so <literal>rats</> does not match <literal>rat</>.
295295 </para>
296296
297- <para>
298- Phrase search is made possible with the help of the <literal><-></>
299- (FOLLOWED BY) operator, which enforces lexeme order. This allows you
300- to discard strings not containing the desired phrase, for example:
301-
302- <programlisting>
303- SELECT q @@ to_tsquery('fatal <-> error')
304- FROM unnest(array[to_tsvector('fatal error'),
305- to_tsvector('error is not fatal')]) AS q;
306- ?column?
307- ----------
308- t
309- f
310- </programlisting>
311-
312- A more generic version of the FOLLOWED BY operator takes form of
313- <literal><N></>, where N stands for the greatest allowed distance
314- between the specified lexemes. The <literal>phraseto_tsquery</>
315- function makes use of this behavior in order to construct a
316- <literal>tsquery</> capable of matching the provided phrase:
317-
318- <programlisting>
319- SELECT phraseto_tsquery('cat ate some rats');
320- phraseto_tsquery
321- -------------------------------
322- ( 'cat' <-> 'ate' ) <2> 'rat'
323- </programlisting>
324- </para>
325-
326297 <para>
327298 The <literal>@@</literal> operator also
328299 supports <type>text</type> input, allowing explicit conversion of a text