# Mistake in routing documentation?

**URL:** <https://discuss.emberjs.com/t/mistake-in-routing-documentation/804>\
**Category:** Uncategorized\
**Created:** [March 30, 2013, 3:54pm UTC](https://discuss.emberjs.com/t/mistake-in-routing-documentation/804 "2013-03-30T15:54:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![abdull](https://avatars.discourse-cdn.com/v4/letter/a/779978/32.png) [@abdull](https://discuss.emberjs.com/u/abdull)\
**Post date:** [March 30, 2013, 3:54pm UTC](https://discuss.emberjs.com/t/mistake-in-routing-documentation/804/1 "2013-03-30T15:54:02Z")

</div>

I’m not sure if `discuss.emberjs.com` is the appropiate place right now to ask documentation questions. Being bold, I’ll ask my question anyway here.

[http://emberjs.com/guides/routing/setting-up-a-controller/](http://emberjs.com/guides/routing/setting-up-a-controller/) currently states:

- “The default setupController hook sets the **`model`** property of the associated controller to the route handler’s model.”

Shouldn’t it instead say:

- “The default setupController hook sets the **`content`** property of the associated controller to the route handler’s model.”

---

<div class="post-metadata">

**Author:** ![teddyzeenny](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/teddyzeenny/32/14243_2.png) [@teddyzeenny](https://discuss.emberjs.com/u/teddyzeenny)\
**Post date:** [March 30, 2013, 5:28pm UTC](https://discuss.emberjs.com/t/mistake-in-routing-documentation/804/2 "2013-03-30T17:28:53Z")

</div>

They both work, `model` is an alias for `content`, you can set any of them, it doesn’t matter.

---

<div class="post-metadata">

**Author:** ![tomdale](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/tomdale/32/14168_2.png) [@tomdale](https://discuss.emberjs.com/u/tomdale)\
**Post date:** [March 30, 2013, 9:32pm UTC](https://discuss.emberjs.com/t/mistake-in-routing-documentation/804/3 "2013-03-30T21:32:58Z")

</div>

`model` is the preferred property, though `content` still works for backwards-compatibility. You should expect `content` to be deprecated in a future release.