refactor (#168): standardize headings

src/guide/migration/data-option.md

@@ -59,7 +59,7 @@ Using the example above, there would only be one possible implementation of the
 </script>
 ```
 
-## How to Migrate
+## Migration Strategy
 
 For users relying on the object declaration, we recommend:
 

src/guide/migration/filters.md

@@ -70,6 +70,6 @@ Using the example above, here is one example of how it could be implemented.
 </script>
 ```
 
-## How to Migrate
+## Migration Strategy
 
 Instead of using filters, we recommend replacing them with computed properties or methods.

src/guide/migration/keycode-modifiers.md

@@ -46,6 +46,6 @@ Since [`KeyboardEvent.keyCode` has been deprecated](https://developer.mozilla.or
 
 As a result, this means that `config.keyCodes` is now also deprecated and will no longer be supported.
 
-## How to Migrate
+## Migration Strategy
 
 For those using `keyCode` in their codbase, we recommend converting them to their kebab-cased named equivalents.

src/guide/migration/render-function-api.md

@@ -75,7 +75,7 @@ export default {
     }
 
     // return the render function
-    return () =>  h(
+    return () => h(
       'div',
       {
         onClick: increment
@@ -122,7 +122,7 @@ In 3.x, the entire VNode props structure is flattened. Using the example from ab
 }
 ```
 
-## How to Migrate
+## Migration Strategy
 
 ### Library Authors
 

src/guide/migration/v-model.md

@@ -138,7 +138,7 @@ In addition to v2 hard-coded `v-model` modifiers like `.trim`, now v3 supports c
 
 Read more about custom `v-model` modifiers in the [Custom Events](../component-custom-events.html#handling-v-model-modifiers) section.
 
-## How to Migrate
+## Migration Strategy
 
 We recommend: