Update docs/networking/ippool.md

Co-authored-by: Lucas Saintarbor <lucas.saintarbor@suse.com>

docs/networking/ippool.md

@@ -25,7 +25,7 @@ An IP pool can have specific scopes, and you can specify the corresponding requi
   - Network is a hard condition. The optional IP pool must match the value of the LB annotation `loadbalancer.harvesterhci.io/network`.
   - Every IP pool, except the global IP pool, has a unique scope different from others if its priority is `0`. The project, namespace, or cluster name of LBs should be in the scope of the IP pool if they want to get an IP from this pool.
 - `spec.selector.priority` specifies the priority of the IP Pool. The larger the number, the higher the priority. If the priority is not `0`, the value should differ. The priority helps you to migrate the old IP pool to the new one.
-- If the IP Pool has a scope that matches all projects, namespaces, and guest clusters, it's called a global IP pool. It's only allowed to have one global IP pool. If there is no IP pool matching the requirements of the LB, the IPAM will allocate an IP from the global IP pool if it exists.
+- If the IP Pool has a scope that matches all projects, namespaces, and guest clusters, it's called a global IP pool, and only one global IP pool is allowed. If there is no IP pool matching the requirements of the LB, the IPAM will allocate an IP address from the global IP pool if it exists.
 
 ### Examples
 - Example 1: We want to configure an IP pool with range `192.168.100.0/24` for the namespace `default`. All the load balancer in the namespace `default` can get an IP from this IP pool. The IP pool will be like that: