doc fixes

docs/yap.tex

@@ -14400,7 +14400,8 @@ Letter = 'D',
 Number = 123456789 ?
 yes
 @end example
-generates the query @example
+generates the query
+@example
 SELECT A.Letter , 'John Doe' , A.Number 
 FROM 'phonebook' A 
 WHERE A.Name = 'John Doe';
@@ -14464,7 +14465,8 @@ above. Assuming the declaration:
 yes
 @end example
 we
-write:@example
+write:
+@example
 ?- db_view(direct_cycle(A,B),(edge(A,B), edge(B,A))). 
 yes 
 ?- direct_cycle(A,B)). 
@@ -14472,7 +14474,8 @@ A = 10,
 B = 20 ?  
 @end example
 This call generates the SQL
-statement: @example
+statement:
+@example
 SELECT A.attr1 , A.attr2
 FROM Edge A , Edge B 
 WHERE B.attr1 = A.attr2 AND B.attr2 = A.attr1;
@@ -14897,7 +14900,8 @@ yes
 The MySQL C API permits two modes for transferring the data generated by
 a query to the client, in our case YAP. The first mode, and the default
 mode used by the MYDDAS-MySQL, is to store the result. This mode copies all the
-information generated to the client side.@example
+information generated to the client side.
+@example
 ?- db_my_result_set(X).
 X=store_result
 yes
@@ -16173,7 +16177,7 @@ be lost.
 We next discuss several issues on trying to make Prolog programs run
 fast in YAP. We assume two different programming styles:
 
-@table @bullet
+@itemize @bullet
 @item Execution of @emph{deterministic} programs often
 boils down to a recursive loop of the form:
 @example
@@ -16182,7 +16186,7 @@ loop(Env) :-
         loop(NewEnv).
 @end example
 
-@end table
+@end itemize
 
 @section Deterministic Programs