Tracking issue for tutorial code/documentation parity

As discussed on the last call, we'll use this to track open issues surrounding party of code and documentation esp. in regards to outdated information like the mention of old api concepts. Most of these are left-overs from the initial conversion process and just need to be updated.

Related issues:

* #108
* #109
* #110
* #111
* #112
* #274
* #251
* #247
* #245
* #179
* #141
* #127
* #122
* #121

Start by reviewing the related issues #108, #109, #110, #111, #112, #274, #251, #247, #245, #179, #141, #127, #122, and #121. Determine which code and documentation mismatches remain, then update the outdated information so the tutorial's code and documentation are consistent.

Written by the indexing model from the issue text.