To me, it seems a little counter intuitive the way this works but it does seem to work. When reviewing the code, it took me a few minutes to realize that the id in the route `/relationships/:id` is a user id and not a relationship id. I found this a little weird at first but it also seems to work nicely in that you don't need to worry about users acting maliciously by deleting relationships that they are not part of (In the solutions, you pass the relationship id into the controller but then you need to add in a line that ensures the follower id is the same as the current user id).