Some minor updates and corrections of sp-implemented.txt.

Docs/sp-implemented.txt

-Stored Procedures implemented 2003-12-10:
-
-
-Summary of Not Yet Implemented:
-
-  - SQL statements using table (like SELECT, INSERT, UPDATE etc)
-    in FUNCTIONs
-  - External languages
-  - Access control
-  - Routine characteristics (mostly used for external languages)
-  - SQL-99 COMMIT (related to BEGIN/END)
-  - FOR-loops
-  - CASCADE/RESTRICT for ALTER and DROP
-  - ALTER/DROP METHOD (as it implies User Defined Types)
-  - SIGNAL and RESIGNAL, and UNDO handlers
+Stored Procedures implemented 2004-01-29:
 
 
 Summary of what's implemented:
@@ -29,6 +15,18 @@ Summary of what's implemented:
   - SHOW DECLARE PROCEDURE/FUNCTION and SHOW PROCEDURE/FUNCTION STATUS
 
 
+Summary of Not Yet Implemented:
+
+  - SQL statements using tables (like SELECT, INSERT, UPDATE etc) in FUNCTIONs
+  - External languages
+  - Access control
+  - SQL-99 COMMIT (related to BEGIN/END)
+  - FOR-loops
+  - CASCADE/RESTRICT for ALTER and DROP
+  - ALTER/DROP METHOD (as it implies User Defined Types)
+  - SIGNAL and RESIGNAL, and UNDO handlers
+
+
 List of what's implemented:
 
   - CREATE PROCEDURE|FUNCTION name ( args ) characteristics body
@@ -91,7 +89,7 @@ List of what's implemented:
       context which makes sharing prepared SPs impossible. And, even when
       this is resolved, it's not necessarily the case that it will be faster
       than a cache per thread. A global cache requires locks, which might
-      become a buttleneck. (It would save memory though.)
+      become a bottleneck. (It would save memory though.)
     - CONDITIONs and HANDLERs are implemented, but not the SIGNAL and
       RESIGNAL statements. (It's unclear if these can be implemented.)
       The semantics of CONDITIONs is expanded to allow catching MySQL error
@@ -102,6 +100,10 @@ List of what's implemented:
       (NEXT, PRIOR, etc). Cursors are ASENSITIVE, READ-ONLY, non-SCROLLing.
       (The additional syntax will be added for completeness, but for the
        most part unsupported with the current underlying cursor mechanism.)
+      N.B. The current implementation is temporary and only works within a
+        stored procedure, and may not perform well for very large result sets.
+        A "real" cursor implementation is under development; this will replace
+        the current one when it's finished.
 
   - SHOW procedures and functions
     SHOW DECLARE PROCEDURE|FUNCTION <name>