MySQL Bugs: #26585: Confusing usage of the word 'row' ("in a row") to describe a sequence of events

Bug #26585	Confusing usage of the word 'row' ("in a row") to describe a sequence of events
Submitted:	23 Feb 2007 1:00	Modified:	23 Feb 2007 1:14
Reporter:	Roland Bouman	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.1	OS:	na
Assigned to:	Paul DuBois	CPU Architecture:	Any

Description:
In http://dev.mysql.com/doc/refman/5.1/en/insert-speed.html, the following text is not as clear as it could be:

"INSERT, UPDATE, and DELETE operations are very fast in MySQL, but you can obtain better overall performance by adding locks around everything that does more than about five inserts or updates in a row. If you do very many inserts in a row, you could do a LOCK TABLES  followed by an UNLOCK TABLES once in a while"

The usage of "row" is confusing (assuming that it is used to describe a succession of eventS)

How to repeat:
see In http://dev.mysql.com/doc/refman/5.1/en/insert-speed.html, the 

Suggested fix:
please reword

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

in a row -> successive