Fix net typo in networking tutorials

`dog-net` shoud be `dognet`,  `cat-net` to `catnet`

Author: bingohuang

networking/tutorials.md

@@ -168,7 +168,7 @@ To accomplish this policy we create a second overlay network, `catnet`, and atta
 $ docker network create -d overlay --subnet 10.2.0.0/24 --gateway 10.2.0.1 catnet
 $ docker service create --network catnet --name cat-db redis
 $ docker service create --network catnet -p 9000:5000 -e 'DB=cat-db' -e 'ROLE=cat' --name cat-web chrch/web
-$ docker service create --network dog-net --network cat-net -p 7000:5000 -e 'DB1=dog-db' -e 'DB2=cat-db' --name admin chrch/admin 
+$ docker service create --network dognet --network catnet -p 7000:5000 -e 'DB1=dog-db' -e 'DB2=cat-db' --name admin chrch/admin 
 ```
 
 This example uses the following logical topology:
@@ -223,4 +223,4 @@ When `dog-web` communicates with `dog-db`, the physical network will route or sw
 
 Docker is a quickly evolving technology, and the networking options are growing to satisfy more and more use cases every day. Incumbent networking vendors, pure-play SDN vendors, and Docker itself are all contributors to this space. Tighter integration with the physical network, network monitoring, and encryption are all areas of much interest and innovation.  
 
-This document detailed some but not all of the possible deployments and CNM network drivers that exist. While there are many individual drivers and even more ways to configure those drivers, we hope you can see that there are only a few common models routinely deployed. Understanding the tradeoffs with each model is key to long term success.
+This document detailed some but not all of the possible deployments and CNM network drivers that exist. While there are many individual drivers and even more ways to configure those drivers, we hope you can see that there are only a few common models routinely deployed. Understanding the tradeoffs with each model is key to long term success.