Yeah.. Table Join with Name Suitability a Success

A little after the fact, but I finally stuck through it and figured this one out with the help of Pete. My final map I turned in cheated because I had 2 layers, one with names and one with suitability. I went so far with the annotation on that map that I ended up keeping in my final map. But... I least I feel better that I finally learned how to make the tables join and display name and suitability all in one table!

Exported Final Map

Removing data from a Geodatabase

I have looked through my current AshevilleBikeMap.gdb and it seems I have many Feature Classes I do not need, or choose not to use for my final map.  Wow, kind of crazy the amount of time I took building some of these Feature Classes because I thought I wanted to use them.  Realize I should have practiced more with the data to determine if it would or would not "fit" into my map presentation.  Wish I would have moved the feature class from the geodatabase as soon as I decided not to use it.  Now I can not remember what some of these classes were when I created them 6 weeks ago.  I feel sure I do not need, yet I am scared to start deleting away the following classes:
BikeCompPlan

BikeRouteNamesAnno
BuncombeBikeShopsAnno
BuncombeBikeShopsAnno2
BuncombeBikeShopsAnno3
BuncombeCountyCensusAddress
BuncombeHydroPolyAnno2
BuncombeHydroPolyAnno3
BuncombeMajorRoads
BuncombeMedicalSites
BuncombeMedicalSites_Clip
BuncombeMedicalSites_Clip1
Contour100foot
Contour20foot
Contour4foot
Lakes__Rivers__Streams_selectionAnnoMeter
NCStateRd
NCStreetsFoot
Political_BoundaryAnno
StateOwnedLand
Streams
Updated_Asheville_Bike_Racks
Waterbody