No worries, I'll rename it.  I primarily didn't include filter in the name based on a couple of thoughts:
1. from a routes perspective, it is a nested resource so the routes shows what the rule is associated with (e.g. content_view_definitions -> filters -> rules)
2. i was thinking that down the road (perhaps even sooner than later), we may want to restructure our controllers directory so that we can better group related controllers.  For example, all content view related controllers could be placed in content views subdirectory.  (Note: the usefulness of this would need to be looked at and discussed since it effectively 'namespaces' the controllers; however, it may simplify things over time as the app gets bigger and bigger).

For now, I'll rename and we can easily rename it again later if we choose to restructure a bit.