Apply suggestions from code review

Co-authored-by: Jessica <[email protected]>

Author: RoRoJ

network/vpc/reference-content/dns.mdx

@@ -44,7 +44,7 @@ The managed DNS resolver service is exposed on each Private Network through the
 - IPv4: `169.254.169.254`
 - IPv6: `fe80::200:22ff:fe05:ca1e`
 
-The service resolves both regular public records, as well as internal VPC records
+The service resolves both regular public records, as well as internal VPC records.
 
 <Message type="tip">
 The `.internal` at the end of internal addresses is important in enabling the resolver to distinguish between internal and external/public DNS. For this reason, you should always add `.internal` when addressing resources within your VPC.
@@ -74,6 +74,6 @@ If you experience problems with DNS, try the following steps:
 
 3. **Check Private Network name**. Issues can arise with Private Networks who share a name with a TLD. See our [dedicated document](/network/vpc/troubleshooting/pn-name/) for more help.
 
-4. **Check whether you are using Network Manager**: DNS does not work out of hte box for Linux distributions using Network Managed, such as **RockyLinux**. Find out how to resolve this problem [in our troubleshooting page](/network/vpc/troubleshooting/private-dns-dhcp-not-working/#distributions-running-network-manager)
+4. **Check whether you are using Network Manager**: DNS does not work out of the box for Linux distributions using Network Managed, such as **RockyLinux**. Find out how to resolve this problem [on our troubleshooting page](/network/vpc/troubleshooting/private-dns-dhcp-not-working/#distributions-running-network-manager)
 
 If you are still having problems reaching a resource attached to a Private Network via its hostname, [open a support ticket](https://console.scaleway.com/support).