Upvote

Resolves all 4 parts of Issue #3 
Resolves part 2 of Issue #10 
Resolves all 3 parts of Issue #11 
Avoid creating deeply nested resources. Only some actions need to be nested while others can be top-level. For example, `/food_trucks/10/reviews/new` can be used to create a review for a food truck with an ID = 10. But once the review is created, you can visit it with `/reviews/15` rather than `/food_trucks/10/reviews/15`. Since you know the ID of the review, you can use that info to find the ID of the food truck.

I would change this to look something like:

```ruby
resources :food_trucks, only: [:index, :show, :new, :create, :destroy] do
  resources :reviews, only: [:create, :destroy]
end

resources :reviews, only: [] do
  resources :votes, only: [:create, :update, :destroy]
end
```