minor typos

DenTelezhkin · Sep 11, 2016 · c3948d9 · c3948d9
1 parent b522a62
commit c3948d9
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 12 deletions.
diff --git a/Documentation/DTTableViewManager 5.0 migration guide.md b/Documentation/DTTableViewManager 5.0 migration guide.md
@@ -150,7 +150,7 @@ Here's full list of all delegate and datasource methods implemented:
 
 | DataSource method | Event method | Comment |
 | ----------------- | ------------ | ------- |
-|  cellForItemAt: | configure(_:_:) | Called after `update(with:)` method was called |
+|  cellForRowAt: | configure(_:_:) | Called after `update(with:)` method was called |
 |  viewForHeaderInSection: | configureHeader(_:_:) | Called after `update(with:)` method was called |
 |  viewForFooterInSection: | configureFooter(_:_:) | Called after `update(with:)` method was called |
 |  commit:forRowAt: | commitEditingStyle(for:_:) | - |

diff --git a/README.md b/README.md
@@ -112,21 +112,19 @@ That's it! It's that easy!
 
 ### Mapping and registration
 
-* `register:`
-* `registerNibNamed:for:`
-* `registerHeader:`
-* `registerNibNamed:forHeader:`
-* `registerFooter:`
-* `registerNibNamed:forFooter:`
-* `registerNiblessHeader:`
-* `registerNiblessFooter`
+* `register(_:)`
+* `registerNibNamed(_:for:)`
+* `registerHeader(_:)`
+* `registerNibNamed(_:forHeader:)`
+* `registerFooter(_:)`
+* `registerNibNamed(_:forFooter:)`
+* `registerNiblessHeader(_:)`
+* `registerNiblessFooter(_:)`
 
 By default, `DTTableViewManager` uses section titles and `tableView(_:titleForHeaderInSection:)` UITableViewDatasource methods. However, if you call any mapping methods for headers or footers, it will automatically switch to using `tableView(_:viewForHeaderInSection:)` methods and dequeue `UITableViewHeaderFooterView` instances. Make your `UITableViewHeaderFooterView` subclasses conform to `ModelTransfer` protocol to allow them participate in mapping.
 
 You can also use UIView subclasses for headers and footers.
 
-For more detailed look at mapping in DTTableViewManager, check out dedicated *[Mapping wiki page](https://github.com/DenHeadless/DTTableViewManager/wiki/Mapping-and-registration)*.
-
 ### Data models
 
 `DTTableViewManager` supports all Swift and Objective-C types as data models. This also includes protocols and subclasses.
@@ -157,7 +155,7 @@ Mappings are resolved simply by calling `is` type-check. In our example Apple is
 
 ### CoreDataStorage
 
-`CoreDataStorage` is meant to be used with ]NSFetchedResultsController]. It automatically monitors all NSFetchedResultsControllerDelegate methods and updates UI accordingly to it's changes. All you need to do to display CoreData models in your UITableView, is create CoreDataStorage object and set it on your `storage` property of `DTTableViewManager`.
+`CoreDataStorage` is meant to be used with `NSFetchedResultsController`. It automatically monitors all NSFetchedResultsControllerDelegate methods and updates UI accordingly to it's changes. All you need to do to display CoreData models in your UITableView, is create CoreDataStorage object and set it on your `storage` property of `DTTableViewManager`.
 
 It also recommended to use built-in CoreData updater to properly update UITableView: