From e8cb509953d86d2f9fd9e03e919482f5d0b9c394 Mon Sep 17 00:00:00 2001
From: Luke Latham <1622880+guardrex@users.noreply.github.com>
Date: Wed, 20 Dec 2017 22:40:42 -0600
Subject: [PATCH 1/2] Refactor instructions on logs folder creation (#5051)

---
 aspnetcore/publishing/iis.md | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/aspnetcore/publishing/iis.md b/aspnetcore/publishing/iis.md
index ba2465425a..85528a8d4d 100644
--- a/aspnetcore/publishing/iis.md
+++ b/aspnetcore/publishing/iis.md
@@ -126,14 +126,7 @@ If you don't have a *web.config* file in the project when you publish with *dotn
 
 1. On the target IIS system, create a folder to contain the app's published folders and files, which are described in [Directory Structure](xref:hosting/directory-structure).
 
-2. Within the folder you created, create a *logs* folder to hold stdout logs (if you plan to enable logging to troubleshoot start-up issues). If you plan to deploy your application with a *logs* folder in the payload, you may skip this step. There's an [open issue to create the folder automatically](https://github.com/aspnet/AspNetCoreModule/issues/30). If you would like MSBuild to create the *log* folder for you, add the following `Target` to your project file:
-
-   ```xml
-   <Target Name="CreateLogsFolder" AfterTargets="AfterPublish">
-     <MakeDir Directories="$(PublishDir)logs" Condition="!Exists('$(PublishDir)logs')" />
-     <MakeDir Directories="$(PublishUrl)logs" Condition="!Exists('$(PublishUrl)logs')" />
-   </Target>
-   ```
+2. Within the folder, create a *logs* folder to hold stdout logs when stdout logging is enabled. If the app is deployed with a *logs* folder in the payload, skip this step. For instructions on making MSBuild create the *logs* folder, see the [Directory structure](xref:hosting/directory-structure) topic.
 
 3. In **IIS Manager**, create a new website. Provide a **Site name** and set the **Physical path** to the app's deployment folder that you created. Provide the **Binding** configuration and create the website.
 

From 2ce86018cc6449850af55e6a13d6abfd65521dcd Mon Sep 17 00:00:00 2001
From: Caro Caserio <CCaserio@moravia.com>
Date: Thu, 21 Dec 2017 20:21:39 -0300
Subject: [PATCH 2/2] CC44770: Update getting-started.md (#5058)

* CC44770: Update getting-started.md

Hello, @rick-anderson,

This proposed file change comes from this Community Contribution: https://github.com/aspnet/Docs.zh-tw/pull/25.

Please, help to check this proposed file change into the article and help to merge if you agree with fix. If not, please, let me know either if you would like me to fix it in another way within this PR, if you prefer to fix it in another PR or if I should close this PR as by-design. In case of using another PR, please, let me know of your PR number, so we can confirm and close this PR.

Many thanks in advance.

* Update getting-started.md
---
 aspnetcore/getting-started.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/aspnetcore/getting-started.md b/aspnetcore/getting-started.md
index 7b7ef97361..fb45720c86 100644
--- a/aspnetcore/getting-started.md
+++ b/aspnetcore/getting-started.md
@@ -21,7 +21,7 @@ uid: getting-started
 
 2. Create a new .NET Core project.
 
-   On macOS and Linux, open a terminal window. On Windows, open a command prompt.
+   On macOS and Linux, open a terminal window. On Windows, open a command prompt. Enter the following command:
 
     ```terminal
     dotnet new razor -o aspnetcoreapp