We're hoping to ramp up on defects soon and I'm wondering if there are some guides on how to use them.  I see the comprehensive documentation on creating them, editing them, etc.  However I'm wondering if there might be a webinar or presentation on how they might be used?

Rally doesn't have strict guidelines on how defects should be maintained as every team has a little different process.  There are some companies who file defects that are attached to the user story so that there is tracking for which acceptance criteria was not completed.  There are also companies that file defects as standalone work products, not associated with any stories or test cases, and prioritize their backlog to include these defects in the next planning session.  There are others who use defect suites to group defects for a particular release or iteration and then "patch" all of the updates at once.

Generally, we recommend that once your defect has been created, the team take a look and determine who is best able or has the capacity to provide the fix.  At this time there will also be some discussion on whether their iteration commitments will be impacted and they should reprioritize or place the defect in the backlog of work to be planned for future iterations or releases.

There are ways for individuals to set up notifications of changes to or assignment of defects and other conditions as well.  Check out this knowlegebase post for some additional details.

As to marking a defect as complete, we would recommend that there be a process similar to what is established for your user stories.  Make sure testers have verified the fix and automated or manual testing has been updated as needed.  There are schedule states and status fields on the defect to identify when they have been resolved or closed so just communicate with your team to ensure everyone is on the same page when filling in values.

Basically there really isn't a "right" way to manage defects.