From 1c8737a68739d792cc18a72c19a3e2c41198d655 Mon Sep 17 00:00:00 2001 From: Ron Petrusha Date: Tue, 12 Dec 2017 09:15:18 -0800 Subject: [PATCH] Removed duplicate words (#583) --- .../compatibility/SerialPort-background-thread-exceptions.md | 4 ++-- Documentation/compatibility/long-path-support.md | 4 ++-- .../compatibility/throttle-concurrent-requests-per-session.md | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/Documentation/compatibility/SerialPort-background-thread-exceptions.md b/Documentation/compatibility/SerialPort-background-thread-exceptions.md index 6396851..9205480 100644 --- a/Documentation/compatibility/SerialPort-background-thread-exceptions.md +++ b/Documentation/compatibility/SerialPort-background-thread-exceptions.md @@ -21,7 +21,7 @@ In applications that target the .NET Framework 4.7.1 or a later version, backgro ### Recommended Action -For apps that target the .NET Framework 4.7.1, you can opt out of the exception handling if it is not desirable by adding the following to to the `` section of your `app.config` file: +For apps that target the .NET Framework 4.7.1, you can opt out of the exception handling if it is not desirable by adding the following to the `` section of your `app.config` file: ```xml @@ -29,7 +29,7 @@ For apps that target the .NET Framework 4.7.1, you can opt out of the exception ``` -For apps that target earlier versions of the .NET Framework but run on the .NET Framework 4.7.1 or later, you can opt in to the exception handling by adding the following to to the `` section of your `app.config` file: +For apps that target earlier versions of the .NET Framework but run on the .NET Framework 4.7.1 or later, you can opt in to the exception handling by adding the following to the `` section of your `app.config` file: ```xml diff --git a/Documentation/compatibility/long-path-support.md b/Documentation/compatibility/long-path-support.md index b0fc3f1..6afeb6e 100644 --- a/Documentation/compatibility/long-path-support.md +++ b/Documentation/compatibility/long-path-support.md @@ -35,7 +35,7 @@ exceeds 260 characters. ### Recommended Action For apps that target the .NET Framework 4.6.2, you can opt out of long path -support if it is not desirable by adding the following to to the `` +support if it is not desirable by adding the following to the `` section of your `app.config` file: ```xml @@ -46,7 +46,7 @@ section of your `app.config` file: For apps that target earlier versions of the .NET Framework but run on the .NET Framework 4.6.2 or later, you can opt in to long path support by adding the -following to to the `` section of your `app.config` file: +following to the `` section of your `app.config` file: ```xml diff --git a/Documentation/compatibility/throttle-concurrent-requests-per-session.md b/Documentation/compatibility/throttle-concurrent-requests-per-session.md index 66078ce..2fbf1ee 100644 --- a/Documentation/compatibility/throttle-concurrent-requests-per-session.md +++ b/Documentation/compatibility/throttle-concurrent-requests-per-session.md @@ -10,7 +10,7 @@ Edge NotPlanned ### Change Description -In the .NET Framework 4.6.2 and earlier, ASP.NET executes requests with the same Sessionid sequentially, and ASP.NET always issues the Sessionid through cookie by default. If a page takes a long time to respond, it will significantly degrade server performance just by pressing F5 on the browser. In the fix, we added a counter to track the queued requests and terminate the requests when they exceed a specified limit. The default value is 50. If the the limit is reached, a warning will be logged in the event log, and an HTTP 500 response may be recorded in the IIS log. +In the .NET Framework 4.6.2 and earlier, ASP.NET executes requests with the same Sessionid sequentially, and ASP.NET always issues the Sessionid through cookies by default. If a page takes a long time to respond, it will significantly degrade server performance just by pressing F5 on the browser. In the fix, we added a counter to track the queued requests and terminate the requests when they exceed a specified limit. The default value is 50. If the limit is reached, a warning will be logged in the event log, and an HTTP 500 response may be recorded in the IIS log. - [x] Quirked - [ ] Build-time break