Repository: google/WebFundamentals (language: javascript)

Issue:
duplicated step 3
**Page Affected:** https://developers.google.com/web/updates/2018/09/inside-browser-part2

**What needs to be done?**

_Please provide description of what's needs to be done here. Please be sure to include the link to the original page
and any supporting links/data._

- [x] should has a correct step counter.

![image](https://user-images.githubusercontent.com/32980314/118385519-1452ce80-b642-11eb-90a8-fc221d7c64a9.png)





Discussion / hints:

Fix patch:
diff --git a/src/content/en/updates/2018/09/inside-browser-part2.md b/src/content/en/updates/2018/09/inside-browser-part2.md
index 0e875fc3130..29f9a118060 100644
--- a/src/content/en/updates/2018/09/inside-browser-part2.md
+++ b/src/content/en/updates/2018/09/inside-browser-part2.md
@@ -119,7 +119,7 @@ alerts to display a warning page. Additionally,
 check happens in order to make sure sensitive cross-site 
 data does not make it to the renderer process.
 
-### Step 3: Find a renderer process
+### Step 4: Find a renderer process
 
 Once all of the checks are done and Network thread is confident that browser should navigate to the 
 requested site, the Network thread tells UI thread that the data is ready. UI thread then finds a 
@@ -140,7 +140,7 @@ if all goes as expected, a renderer process is already in standby position when
 received data. This standby process might not get used if the navigation redirects cross-site, in 
 which case a different process might be needed.
 
-### Step 4: Commit navigation
+### Step 5: Commit navigation
 
 Now that the data and the renderer process is ready, an IPC is sent from the browser process to the 
 renderer process to commit the navigation. It also passes on the data stream so the renderer 


Test patch: