Update content/en/docs/concepts/policy/resource-quotas.md

Co-authored-by: Tim Bannister <tim@scalefactory.com>

content/en/docs/concepts/policy/resource-quotas.md

@@ -146,8 +146,8 @@ Refer to [Logging Architecture](/docs/concepts/cluster-administration/logging/)
 
 ## Object Count Quota
 
-You can set quota for the total number of certain resources of all standard,
-namespaced resource types using the following syntax:
+You can set quota for **the total number of one particular resource**
+for certain resources of all standard, namespaced resource types using the following syntax:
 
 * `count/<resource>.<group>` for resources from non-core groups
 * `count/<resource>` for resources from the core group
@@ -168,14 +168,14 @@ Here is an example set of resources users may want to put under object count quo
 The same syntax can be used for custom resources.
 For example, to create a quota on a `widgets` custom resource in the `example.com` API group, use `count/widgets.example.com`.
 
-When using `count/*` resource quota (only available for some object kinds), an object is charged
+When using such a resource quota (only available for some object kinds), an object is charged
 against the quota if the control plane has a stored copy.
 These types of quotas are useful to protect against exhaustion of storage resources.  For example, you may
 want to limit the number of Secrets in a server given their large size. Too many Secrets in a cluster can
 actually prevent servers and controllers from starting. You can set a quota for Jobs to protect against
 a poorly configured CronJob. CronJobs that create too many Jobs in a namespace can lead to a denial of service.
 
-It is also possible to do generic object count quota on a limited set of resources.
+There is another syntax only to set the same type of quota for certain resources.
 The following types are supported:
 
 | Resource Name | Description |
@@ -195,7 +195,7 @@ created in a single namespace that are not terminal. You might want to set a `po
 quota on a namespace to avoid the case where a user creates many small pods and
 exhausts the cluster's supply of Pod IPs.
 
-You can find more examples on [Viewing and Setting Quotas](/docs/concepts/policy/resource-quotas/#viewing-and-setting-quotas).
+You can find more examples on [Viewing and Setting Quotas](#viewing-and-setting-quotas).
 
 ## Quota Scopes