DEVEL_BLOG.md in rspreadsheet-0.2.9 vs DEVEL_BLOG.md in rspreadsheet-0.2.10

@@ -1,10 +1,10 @@
 See [GUIDE.md](GUIDE.md#conventions) for syntax conventions.
 
 ## Ideas/wishlist
 
-  * In future inntroduce syntax like ``sheet.range('C3:E4')`` for mass operations. Also maybe ``sheet.cells('C3')`` or ``sheet.cells(3, 'C')`` etc.
+  * In future inntroduce syntax like `sheet.range('C3:E4')` for mass operations.
   * Trying to make row Enumerable - perhaps skipping empty or undefined cells.
   * Maybe insted two syntaxes for accessing cell, we make both of them do the same and return Proxy object which would act either as value or cell.
   * Document that there is a little distinction betwean RSpreadsheet and RSpreadsheet::Workbook. The former delegates everythink to the other.
   * allow `book.worskheets.first` syntax
   * allow `sheet.cells.sum { |cell| cell.value }
@@ -17,10 +17,13 @@
   * xml document is always synchronized with the data. So the save is trivial.
   * no duplication of data. Objects like RowArray should containg minimum information. This one exists solely to speed up cell search. Taken to extream it is questionable, whether we need such objects at all, it might be possible to always work with xml directly.
   * all cells and rows only server as proxy. they hold index and worksheet pointer and everytime read or write is done, the xml is newly searched. until there is a xmlnode caching we have no problem
   * all cells returned for particular coordinates are **always the same object**. This way we have no problem to synchronize changes.
     
+## Known Issues
+  * currently there is a confusing syntax @worksheet.rows(1).cells[5] which returns a cell object in SIXT column, which is not intended. It is side effecto of Row#cells returning an array
+    
 ## Developing this gem
 
 ### Automated testing
 
   * ``bundle exec guard`` will get tested any changes as soon as they are summitted
@@ -33,10 +36,10 @@
   * [coverals](https://coveralls.io/r/gorn/rspreadsheet) checks how well source is covered by tests
 
 ### Local testing and releasing (to github and rubygems).
 
 1. make changes
-2. test if all tests pass (run `bundle exex guard` to test automatically). If not go to 1
+2. test if all tests pass (run `bundle exec guard` to test automatically). If not go to 1
 3. build and install locally
     * ``rake build`` - builds the gem to pkg directory (if something gets wrong, sometimes comit go git gelps)
     * ``sudo rake install`` - installs gem to local system [^1]
 4. Now can locally and manually use/test the gem. This should not be replacement for automated testing. If you make some changes, go to 1.
 5. When happy, increment the version number and `git add .; git commit -am'commit message'; git push`