From 56a458d47743d605588220b80c0967573fde193a Mon Sep 17 00:00:00 2001
From: ZYSzys <17367077526@163.com>
Date: Thu, 25 Oct 2018 11:16:24 +0800
Subject: [PATCH 1/2] doc: fix syntax in doc/api/path.md

---
 doc/api/path.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/api/path.md b/doc/api/path.md
index 2a1f06028ee6f4..c7a64386458195 100644
--- a/doc/api/path.md
+++ b/doc/api/path.md
@@ -20,7 +20,7 @@ paths are being used.
 
 For example, using the `path.basename()` function with the Windows file path
 `C:\temp\myfile.html`, will yield different results when running on POSIX than
-when run on Windows:
+when running on Windows:
 
 On POSIX:
 

From 644b9755f33fd209087b8473d387fce487aad3ef Mon Sep 17 00:00:00 2001
From: ZYSzys <17367077526@163.com>
Date: Thu, 25 Oct 2018 12:59:53 +0800
Subject: [PATCH 2/2] doc: simplify path.basename() on POSIX and Windows

---
 doc/api/path.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/doc/api/path.md b/doc/api/path.md
index c7a64386458195..c04bff0c476f46 100644
--- a/doc/api/path.md
+++ b/doc/api/path.md
@@ -18,9 +18,7 @@ on which a Node.js application is running. Specifically, when running on a
 Windows operating system, the `path` module will assume that Windows-style
 paths are being used.
 
-For example, using the `path.basename()` function with the Windows file path
-`C:\temp\myfile.html`, will yield different results when running on POSIX than
-when running on Windows:
+So using `path.basename()` might yield different results on POSIX and Windows:
 
 On POSIX: