Rename permission docs path to plural (#11648)

* Rename permission docs path to plural

Signed-off-by: Joon Park <joonp@spotify.com>

* Update todo list plugin READMEs

Signed-off-by: Joon Park <joonp@spotify.com>

docs/permissions/getting-started.md

@@ -152,6 +152,6 @@ permission:
 
 3. Now that you’ve made this change, you should find that the unregister entity menu option on the catalog entity page is disabled.
 
-![Entity detail page showing disabled unregister entity context menu entry](../assets/permission/disabled-unregister-entity.png)
+![Entity detail page showing disabled unregister entity context menu entry](../assets/permissions/disabled-unregister-entity.png)
 
 Now that the framework is fully configured, you can craft a permission policy that works best for your organization by utilizing a provided authorization method or by [writing your own policy](./writing-a-policy.md)!

docs/permissions/overview.md

@@ -22,7 +22,7 @@ The permission framework was designed with a few key properties in mind:
 
 - **Integrators** can author or configure policies that define which users can take certain actions upon which resources.
 
-![](../assets/permission/permission-framework-overview.drawio.svg)
+![](../assets/permissions/permission-framework-overview.drawio.svg)
 
 1. The user triggers a request to perform some action. The request specifies the authorization details using the permission specified by the plugin (in this case, a resource read action).
 

docs/permissions/plugin-authors/01-setup.md

@@ -105,7 +105,7 @@ The source code is available here:
 
 Now if you start your application you should be able to reach the `/todo-list` page:
 
-![Todo List plugin page](../../assets/permission/permission-todo-list-page.png)
+![Todo List plugin page](../../assets/permissions/permission-todo-list-page.png)
 
 ---