Update client guidelines according to previous conversations in matrix (

#1251)

docs/general/clients/index.mdx

@@ -32,15 +32,16 @@ Please verify it meets the requirements below and [submit a pull request](https:
 
 ### Requirements for Inclusion in All Clients
 
-- Any client meeting the following requirements:
-  - Must be aligned with the [Jellyfin Community Standards](/docs/general/community-standards).
-    - In particular the client must **NOT** engage in, encourage, or facilitate piracy.
-    - The developer must be in good community standing in accordance to the Community Standards.
-  - Must adhere to the [Jellyfin Branding Guidelines](/docs/general/contributing/branding) including usage of the Jellyfin name.
-    - This includes usage of the Jellyfin name or `org.jellyfin` namespace that could hinder the ability to publish an official client to a store in the future.
-  - Must include first rate support for Jellyfin servers. (i.e. Support for Jellyfin should be a primary function or at the same level of integration of any other supported services.)
-  - Must **NOT** be specific to or intended to promote a specific hosted Jellyfin server instance.
-  - Must have clear open-source licensing and be void of any known issues related to attribution, copyright, or license violations.
+Clients must meet the following guidelines for inclusion in the list of all clients:
+
+- Must be aligned with the [Jellyfin Community Standards](/docs/general/community-standards).
+  - In particular, the client must **NOT** engage in, encourage, or facilitate piracy.
+  - The developer must be in good community standing in accordance to the Community Standards.
+- Must adhere to the [Jellyfin Branding Guidelines](/docs/general/contributing/branding), including usage of the Jellyfin name, trademarks and icons.
+  - This includes usage of the Jellyfin name or `org.jellyfin` namespace that could hinder the ability to publish an official client to a store in the future.
+- Must include first rate support for Jellyfin servers. (i.e. Support for Jellyfin should be a primary function or at the same level of integration of any other supported services.)
+- Must **NOT** be specific to or intended to promote a specific hosted Jellyfin server instance.
+- Must have clear licensing and be void of any known issues related to attribution, copyright, or license violations.
 
 The final decision for inclusion is at the discretion of the Jellyfin Contributor Team following the decision-making guidelines in the [Jellyfin Constitution](https://github.com/jellyfin/jellyfin-meta/blob/master/policies-and-procedures/jellyfin-constitution.md).