Skip to content

Commit d8b227e

Browse files
RoRoJjcirinosclwy
andauthored
Apply suggestions from code review
Co-authored-by: Jessica <[email protected]>
1 parent 7b3796c commit d8b227e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

pages/vpc/troubleshooting/connectivity-tests.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ It is particularly useful to carry out these steps before opening a support tick
3131

3232
2. Try to reach the non-communicating Instance with a ping via `ping instance-name` (where `instance-name` is the name you gave your Instance upon creation.)
3333

34-
3. Carry out the same test for both IPv4 and IPv6, ie `ping -4 instance-name` and `ping -6 instance-name`
34+
3. Carry out the same test for both IPv4 and IPv6, ie `ping -4 instance-name` and `ping -6 instance-name`.
3535

3636
- If these tests fail, there may be a DNS issue meaning the Instance's hostname cannot be resolved, see step 4 directly below.
3737
- Otherwise, if the tests succeed, continue to the section [Verify ARP table](#step-2-verify-artp-table)
@@ -54,7 +54,7 @@ A server's **A**ddress **R**esolution **P**rotocol (ARP) table maps IP addresses
5454
172.16.8.2 dev ens5 lladdr 02:00:00:1c:0d:9b REACHABLE
5555
```
5656

57-
2. Find the line beginning with the non-communicating Instance's private IP address, and containing also its MAC address (you can check both via the Scaleway console in the Private Network's **Attached resources** tab.)
57+
2. Find the line beginning with the non-communicating Instance's private IP address, and containing also its MAC address (you can check both via the Scaleway console in the Private Network's **Attached resources** tab).
5858

5959
The line ends with the state of the probe for that Instance's MAC address.
6060

@@ -64,7 +64,7 @@ A server's **A**ddress **R**esolution **P**rotocol (ARP) table maps IP addresses
6464

6565
### Step 3: Try reaching the Instance using its LLA
6666

67-
If the Instance could not be reached via resolution of its MAC address, next you should try to reach it via its IPv6 **L**ink **L**ocal **A**ddress (LLA) in the Private Network.
67+
If the Instance could not be reached via the resolution of its MAC address, next you should try to reach it via its IPv6 **L**ink **L**ocal **A**ddress (LLA) in the Private Network.
6868

6969
The LLA is calculated from the Instance's MAC address.
7070

0 commit comments

Comments
 (0)