Update service name in example of Name based virtual hosting

`service2` is mapped to `second.bar.com` in the given example

```
- host: second.bar.com
    http:
      paths:
      - pathType: Prefix
        path: "/"
        backend:
          service:
            name: service2
            port:
              number: 80
```

content/en/docs/concepts/services-networking/ingress.md

@@ -378,7 +378,7 @@ web traffic to the IP address of your Ingress controller can be matched without
 virtual host being required.
 
 For example, the following Ingress routes traffic
-requested for `first.bar.com` to `service1`, `second.foo.com` to `service2`, and any traffic
+requested for `first.bar.com` to `service1`, `second.bar.com` to `service2`, and any traffic
 to the IP address without a hostname defined in request (that is, without a request header being
 presented) to `service3`.