Update docs/networking/ippool.md

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

docs/networking/ippool.md

@@ -28,7 +28,7 @@ An IP pool can have specific scopes, and you can specify the corresponding requi
 - 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:
+- **Example 1:** You want to configure an IP pool with the range `192.168.100.0/24` for the namespace `default`. All the load balancers in the namespace `default` get an IP from this IP pool. For an example, refer to the following `.yaml`:
 
   ```yaml
   apiVersion: networking.harvesterhci.io/v1beta1