added a test in the authentication_pages_spec to check to make sure a non-signed in user was redirected when trying to send a post or a delete request to the relationships controller.  This naturally checks the instance of the follow and unfollow buttons which use post and delete respectively.
created the relationships_controller which checks to see if a user is signed in and has a create and destroy method.  the create method finds the user to be followed using the params :relationship and :followed_id - followed_id is passed from the form - and not sure how the :relationship is passed.  the destroy method finds the user to be destroyed from the :id params passed and the person corresponding to that followed person - pretty sure it's just taking teh current user and calling the relationship.find method with the :id passed through the param.  then the current user unfollowesBANG and redirects to the page of teh person they just unfollowed - same redirect for the follow
updated partials with the remote: true options os that they implement Ajax
created a controllers spec for the RelationshipsController to check Ajax requests are responded to correctly.  Uses factory girl to create :user and :other_user, then signs in the user, and does both a post and a delete requests to a relationship between teh two users.  it checks the counts in the Relationship model to see if it has changed.
adjusted the controller for relationships, RelationshipsController to use the respond_to method to repond to html and javascript (AJAX) request appropriately.  In the case of html, it just redirects to teh @user as usual.  In the case of the .js, Rails with automatically call a .js.erb file with the same name as the action, i.e.e create.js.erb or destroy.js.erb.  I now have to create those files.