Fix edit links by moving docs content under a dedicated subdirectory

docs/concepts/eventing-resources/brokers.md

@@ -1,28 +0,0 @@
----
-audience: developer
-components:
-  - eventing
-function: explanation
----
-
-# Brokers
-
---8<-- "about-brokers.md"
-
-## Related concepts
-
-### Triggers
-
---8<-- "about-triggers.md"
-
-### Subscribers
-
---8<-- "about-subscribers.md"
-
-<!--
-## Additional resources
-
-## Next steps
-
-Placeholder to add these later
--->

docs/docs/.nav.yml

@@ -2,14 +2,7 @@ nav:
 ###############################################################################
     # Concepts
 ###############################################################################
-    - Concepts:
-      - Overview: concepts/README.md
-      - Resources:
-        - Serving resources:
-          - Revisions: concepts/serving-resources/revisions.md
-        - Eventing resources:
-          - Brokers: concepts/eventing-resources/brokers.md
-      - Duck types: concepts/duck-typing.md
+    - Overview: README.md
 ###############################################################################
     # Getting started
 ###############################################################################
@@ -214,6 +207,7 @@ nav:
           - Developer configuration options: eventing/brokers/broker-developer-config-options.md
         - Triggers:
           - Using Triggers: eventing/triggers/README.md
+        - Duck types: concepts/duck-typing.md
         - Event sources:
           - About event sources: eventing/sources/README.md
           - ApiServerSource:

docs/docs/README.md

@@ -74,7 +74,7 @@ These components can be used independently or together, allowing you to adopt Kn
 
 ### Request Flow in Serving
 
-![Knative Serving data flow: requests arrive at an HTTP router, then travel to either the activator or a pod with a queue-proxy and the user application. The Knative autoscaler collects metrics from the activator and the queue-proxy to determine how many pods to run.](../serving/images/request-flow.png){draggable=false}
+![Knative Serving data flow: requests arrive at an HTTP router, then travel to either the activator or a pod with a queue-proxy and the user application. The Knative autoscaler collects metrics from the activator and the queue-proxy to determine how many pods to run.](./serving/images/request-flow.png){draggable=false}
 
 When a request is made to a Knative Service: