From 9beca81870158cea91bfcb22c4587b734cf6e5e3 Mon Sep 17 00:00:00 2001 From: Caro Caserio Date: Thu, 22 Feb 2018 13:13:27 -0300 Subject: [PATCH] M23065: Truncated sentence (#422) Hello, @dragon119, Translator has reported possible source content issue. Please, help to check my 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. --- docs/best-practices/cdn.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/best-practices/cdn.md b/docs/best-practices/cdn.md index 9090f999a43..64015b60cee 100644 --- a/docs/best-practices/cdn.md +++ b/docs/best-practices/cdn.md @@ -91,5 +91,3 @@ If you deliver static assets such as font files by using the CDN, you might enco ### CDN fallback Consider how your application will cope with a failure or temporary unavailability of the CDN. Client applications may be able to use copies of the resources that were cached locally (on the client) during previous requests, or you can include code that detects failure and instead requests resources from the origin (the application folder or Azure blob container that holds the resources) if the CDN is unavailable. - -The following example shows a fallback mecha