diff --git a/src/internet/doc/ipv6.rst b/src/internet/doc/ipv6.rst
index 5d0f9106d..e7af4bfef 100644
--- a/src/internet/doc/ipv6.rst
+++ b/src/internet/doc/ipv6.rst
@@ -207,7 +207,7 @@ and ``examples/ipv6/radvd-two-prefix.cc``.
 
 Note that the router (i.e., the node with :cpp:class:`Radvd`) will have to have a global address,
 while the nodes using the auto-generated addresses (SLAAC) will have to have a link-local address.
-This is accomplised using :cpp:class:`Ipv6AddressHelper::AssignWithoutAddress`, e.g.:
+This is accomplished using :cpp:class:`Ipv6AddressHelper::AssignWithoutAddress`, e.g.:
 
 ::
 
@@ -232,7 +232,7 @@ IPv6 adds the concept of "on-link" for addresses and prefixes. Simplifying the c
 network with the on-link property behaves roughly as IPv4: a node will assume that any address
 belonging to the on-link prefix is reachable on the link, so it uses Neighbor Discovery Protocol (NDP)
 to find the MAC address corresponding to the IPv6 address.
-If the prefix is not marked as "on-link", then any packet is sent to the defult router.
+If the prefix is not marked as "on-link", then any packet is sent to the default router.
 
 :cpp:class:`Radvd` can announce prefixes that have the on-link flag not set. Moreover, it is possible
 to add an address to a node without setting the on-link property for the prefix used in the address.
diff --git a/src/internet/doc/routing-overview.rst b/src/internet/doc/routing-overview.rst
index 5b5518c5b..da490b27b 100644
--- a/src/internet/doc/routing-overview.rst
+++ b/src/internet/doc/routing-overview.rst
@@ -358,10 +358,10 @@ The reason are the Triggered Updates, together with the fact that when a
 router invalidates a route, it will immediately propagate the route 
 unreachability, thus preventing most of the issues described in the RFC.
 
-However, with complex toplogies, it is still possible to have route 
+However, with complex topologies, it is still possible to have route 
 instability phenomena similar to the one described in the RFC after a 
 link failure. As a consequence, all the considerations about Split Horizon
-remanins valid.
+remains valid.
 
 
 Default routes
@@ -390,7 +390,7 @@ selected on a per-node basis, with the choices being "no split horizon",
 and :rfc:`1058` for a complete discussion on the split horizoning strategies.
 
 Moreover, it is possible to use a non-standard value for Link Down Value (i.e.,
-the value after which a link is considered down). The defaul is value is 16. 
+the value after which a link is considered down). The default is value is 16. 
 
 Limitations
 ~~~~~~~~~~~