Fix createResource state for errored (typo) (#1133)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

Author: thomasvanlankveld

src/routes/reference/basic-reactivity/create-resource.mdx

@@ -94,15 +94,15 @@ const [user] = createResource(() => params.id, fetchUser, {
 #### v1.5.0
 
 1. We've added a new state field which covers a more detailed view of the Resource state beyond `loading` and `error`. 
-You can now check whether a Resource is `unresolved`, `pending`, `ready`, `refreshing`, or `error`.
+You can now check whether a Resource is `unresolved`, `pending`, `ready`, `refreshing`, or `errored`.
 
 | State        | Value resolved | Loading | Has error |
 | ------------ | -------------- | ------- | --------- |
 | `unresolved` | No             | No      | No        |
 | `pending`    | No             | Yes     | No        |
 | `ready`      | Yes            | No      | No        |
 | `refreshing` | Yes            | Yes     | No        |
-| `error`      | No             | No      | Yes       |
+| `errored`    | No             | No      | Yes       |
 
 2. When server-rendering resources, especially when embedding Solid in other systems that fetch data before rendering, you might want to initialize the resource with this prefetched value instead of fetching again and having the resource serialize it in its own state.
 You can use the new `ssrLoadFrom` option for this.