diff --git a/docs/v1.x-migration.md b/docs/v1.x-migration.md
index 38bb000a..e67efcb5 100644
--- a/docs/v1.x-migration.md
+++ b/docs/v1.x-migration.md
@@ -21,6 +21,7 @@
 - [`xlink` namespace required](#xlink-namespace-required)
 - [Nested arrays in views](#nested-arrays-in-views)
 - [`vnode` equality checks](#vnode-equality-checks)
+- [`m.startComputation`/`m.endComputation` removed](#mstartcomputationmendcomputation-removed)
 - [Synchronous redraw removed](#synchronous-redraw-removed)
 
 ---
@@ -444,7 +445,9 @@ var Component = {
 
 ## m.request
 
-Promises returned by [m.request](request.md) are no longer `m.prop` getter-setters. In addition, `initialValue` is no longer a supported option.
+Promises returned by [m.request](request.md) are no longer `m.prop` getter-setters. In addition, `initialValue`, `unwrapSuccess` and `unwrapError` are no longer supported options.
+
+In addition, requests no longer have `m.startComputation`/`m.endComputation` semantics. Instead, redraws are always triggered when a request promise chain completes (unless `background:true` is set).
 
 ### `v0.2.x`
 
@@ -547,6 +550,12 @@ If a vnode is strictly equal to the vnode occupying its place in the last draw,
 
 ---
 
+## `m.startComputation`/`m.endComputation` removed
+
+They are considered anti-patterns and have a number of problematic edge cases, so they no longer exist in v1.x
+
+---
+
 ## Synchronous redraw removed
 
 In v0.2.x it was possible to force mithril to redraw immediately by passing a truthy value to `m.redraw()`. This behavior complicated usage of `m.redraw()` and caused some hard-to-reason about issues and has been removed.