docs(common): clarify wording on themes cdn

marin-bratanov · marin-bratanov · commit 48643b71b175 · 2019-08-15T10:04:34.000+03:00
diff --git a/_contentTemplates/common/js-interop-file.md b/_contentTemplates/common/js-interop-file.md
@@ -69,7 +69,7 @@
           <script src="https://kendo.cdn.telerik.com/blazor/{{site.uiForBlazorLatestVersion}}/telerik-blazor.min.js" defer></script>
         </head>
         
-    Make sure that the version in the URL matches the version of the Telerik UI for Blazor package.
+    >note Make sure that the version in the URL matches the version of the Telerik UI for Blazor package.
 
 #end
 
diff --git a/getting-started/client-blazor.md b/getting-started/client-blazor.md
@@ -47,7 +47,7 @@ For client-side `Blazor App`, we recommend the usage of `Blazor (ASP.NET Hosted)
          ![Add Telerik Blazor Package to Client Project](images/add-telerik-nuget-to-client-app.png)
 
         
-1. Open the `~/wwwroot/index.html` file in the client web application and register the [Theme stylesheet]({%slug general-information/themes%}) (make sure to use the correct version that matches the official Kendo UI for jQuery release number):
+1. Open the `~/wwwroot/index.html` file in the client web application and register the [Theme stylesheet]({%slug general-information/themes%}):
 
     **HTML**
     
diff --git a/getting-started/what-you-need.md b/getting-started/what-you-need.md
@@ -55,7 +55,7 @@ To have the Telerik Blazor components look and behave as expected in the browser
             <link rel="stylesheet" href="https://unpkg.com/@progress/kendo-theme-default@latest/dist/all.css" />
         </head>
         
-    For a server-side app, escape the `@` symbols as `@@`.
+    >note For a server-side app, escape the `@` symbols as `@@`.
 
 * Our JS Interop file. It provides features that cannot be implemented with native Blazor.
 
diff --git a/themes.md b/themes.md
@@ -36,7 +36,7 @@ To use a theme, you must reference its stylesheet in the `<head>` of your main i
 </html>
 ````
 
->note The way bundling and resources will be used in Blazor is still unclear (see [the issue on embedded resources](https://github.com/aspnet/AspNetCore/issues/6349)). Until then, you can use the unpkg workaround above, or local dependency management as described below. Once this matter is decided upon by Microsoft, we will update this information with a proper CDN.
+>note We are considering a better CDN option. Until then, you can use the unpkg workaround above, or local dependency management as described below.
 
 ## Optional Dependency Management
 
