edits to the post

Author: yyx990803

src/_posts/common-gotchas.md

@@ -15,7 +15,7 @@ Most of the time, when you change a Vue instance's data, the view updates. But t
 
 2. When you modify an Array by directly setting an index (e.g. `arr[0] = val`) or modifying its `length` property. Similarly, Vue.js cannot pickup these changes. Always modify arrays by using an Array instance method, or replacing it entirely. Vue provides a convenience method `arr.$set(index, value)` which is just syntax sugar for `arr.splice(index, 1, value)`.
 
-Further reading: [Reactivity in Depth](/guide/reactivity.html).
+Further reading: [Reactivity in Depth](/guide/reactivity.html) and [Array Change Detection](http://vuejs.org/guide/list.html#Array_Change_Detection).
 
 ### When is the DOM updated?
 
@@ -33,4 +33,6 @@ Further reading: [Component Option Caveats](/guide/components.html#Component_Opt
 
 All Vue.js templates are valid, parsable HTML markup, and Vue.js relies on spec-compliant parsers to process its templates. However, as specified in the standard, HTML is case-insensitive when matching tag and attribute names. This means camelCase attributes like `:myProp="123"` will be matched as `:myprop="123"`. As a rule of thumb, you should use camelCase in JavaScript and kebab-case in templates. For example a prop defined in JavaScript as `myProp` should be bound in templates as `:my-prop`.
 
-We are discussing the possibility of eliminating this inconsistency by resolving props and components in a case-insensitive manner as well. Join the conversation [here](https://github.com/vuejs/vue/issues/2308).
+Further reading [camelCase vs. kebab-case](http://vuejs.org/guide/components.html#camelCase_vs-_kebab-case).
+
+We are also discussing the possibility of eliminating this inconsistency by resolving props and components in a case-insensitive manner as well. Join the conversation [here](https://github.com/vuejs/vue/issues/2308).