Clean up note made spurious by guidance change. (#203)

aep/general/0157/aep.md.j2

@@ -60,11 +60,6 @@ number of permutations to the user:
 - APIs **may** add fields to a given view over time. APIs **must not** remove a
   field from a given view (this is a breaking change).
 
-  **Note:** If a service requires (or might require) multiple views with
-  overlapping but distinct values, there is a potential for a namespace
-  conflict. In this situation, the service **should** nest the view enum within
-  the individual resource.
-
 **Note:** The implicit `PATH_ONLY` view described by
 [resource association via embedded resources](.association/#embedded-resources)
 **should not** be explicitly defined in the view enum.