Before we fix the controller issue, we need to take a quick detour and

show you a better way to create links within your own app.

Having the type /pages/page.id everywhere you want to link to an individual

page is tedious and they are prone.

If we want we can name the route.

This will have Rails create a path helper method for

us that will return that same path string.

In rounds.rb add in as arguments on the end of the row with a string value,

that string will be used as the route name.

It can be anything we want but since this is a route to get a single page,

a name of page would be conventional.

Save that.

Now in the index template you can replace /pages/page.id with page_path(page).

It will look at the ID of the model object you pass in, and

return a string with a path that includes that ID.

If we save that and

reload our list of all pages, you'll see the result is the same path string.

We can even skip calling page_path explicitly and

just pass the page object as an argument to link two.

Behind the scenes link two will call page_path on the object for us.

And you can see the result is the very same path string.

So now you know how to name a route and how it can clean up your code.

It's almost always better to name a route and use the helper methods it creates,

rather than littering your code with path strings.

It just keeps things cleaner.

Okay that little detour is out of the way.

But we're still getting an error when we try to click on the link to show

an individual page.

We'll work on that next.