chore(common): fix links

ntacheva · ntacheva · commit 51bc00455459 · 2024-11-04T13:07:53.000+02:00
diff --git a/components/wizard/structure/stepper.md b/components/wizard/structure/stepper.md
@@ -22,7 +22,7 @@ You can use the parameters the `WizardStep` exposes to customize the following p
 * [Individual Stepper settings](#individual-stepper-settings)
     * [Indicators](#indicators)
     * [Labels](#labels)
-    * [Optional](#state)
+    * [Optional](#optional)
     * [Disabled](#disabled)
     * [Valid](#valid)
 
diff --git a/deployment/ci-cd-build-server.md b/deployment/ci-cd-build-server.md
@@ -107,7 +107,7 @@ Finally, you need a `NuGet.Config` file that lists the Telerik server in the `pa
 
 When building or restoring Blazor apps in Docker, the crucial steps are:
 
-1. Have a `NuGet.Config` file in the project or solution folder. The file can [define the Telerik NuGet feed]({%slug installation/nuget%}#edit-the-nugetconfig-file), but without the credentials (Telerik account or NuGet API key).
+1. Have a `NuGet.Config` file in the project or solution folder. The file can [define the Telerik NuGet feed]({%slug installation/nuget%}#edit-the-nuget-config-file), but without the credentials (Telerik account or NuGet API key).
 1. Copy the `NuGet.Config` file together with the `.csproj` file(s) to the Docker image.
 1. [Add](https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-nuget-add-source) or [update](https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-nuget-update-source) the Telerik NuGet feed with the [stored Telerik NuGet credentials (secrets)]({%slug installation/nuget-keys%}). When specifying the `NuGet.Config` file location, note that file names are case-sensitive on Unix systems.
 1. Restore or build the Blazor app.
diff --git a/deployment/nuget-keys.md b/deployment/nuget-keys.md
@@ -52,8 +52,8 @@ The examples below assume that the secret environment variable name is `TELERIK_
 
 There are two common ways to use a [stored NuGet key](#storing-nuget-keys) with the Telerik NuGet server during a build:
 
-* [Using a NuGet.Config file](#using-a-nugetconfig-file)
-* [Using only CLI commands](#using-only-cli-commands)
+* [Using a NuGet.Config file](#using-a-nuget-config-file)
+* [Using only CLI commands](#using-net-cli-commands)
 
 For more information on how to use NuGet keys in a build, check the [Announcing NuGet Keys](https://www.telerik.com/blogs/announcing-nuget-keys) blog post by Lance McCarthy.
 
diff --git a/deployment/troubleshooting.md b/deployment/troubleshooting.md
@@ -21,9 +21,9 @@ This page provides information for common issues you may encounter while deployi
 At the time of writing, sometimes the following issues have been reported that pertain to the Telerik UI for Blazor suite:
 
 * `Unable to find package Telerik.UI.for.Blazor` is a common pitfall in build environments. See the [NuGet Troubleshooting]({%slug troubleshooting-nuget%}#unable-to-find-package) article, which also provides other NuGet-related tips.
-* [404 not found for telerik-blazor.js](#404-not-found-for-telerik-blazorjs)
+* [404 not found for telerik-blazor.js](#404-not-found-for-telerik-blazor-js)
 * [Trial Message](#trial-message)
-* [Could not load file or assembly 'System.Text.Json, ...](#could-not-load-file-or-assembly-systemtextjson-)
+* [Could not load file or assembly 'System.Text.Json, ...](#could-not-load-file-or-assembly-system-text-json)
 * [Blazor Server app is slow or breaks in the cloud](#blazor-server-slow-or-breaks-up-in-the-cloud)
 * [The remote certificate is invalid because of errors in the certificate chain](#invalid-certificate)
 
diff --git a/getting-started/hybrid-blazor.md b/getting-started/hybrid-blazor.md
@@ -33,7 +33,7 @@ The process for adding Telerik UI for Blazor to a WinForms, WPF, or MAUI app is
 
 ### 1. Get the Telerik UI for Blazor Package
 
-To use the  UI for Blazor components, install the `Telerik.UI.for.Blazor` package and include its reference in the `.csproj` file of the app. [Read more on where to get the `Telerik.UI.for.Blazor` package...]({%slug getting-started/what-you-need%}#getting-the-telerik-packages)
+To use the  UI for Blazor components, install the `Telerik.UI.for.Blazor` package and include its reference in the `.csproj` file of the app. [Read more on where to get the `Telerik.UI.for.Blazor` package...]({%slug getting-started/what-you-need%}#nuget-packages)
 
 ### 2. Add the Telerik Client Assets
 
diff --git a/getting-started/vs-code-integration/convert-project-wizard.md b/getting-started/vs-code-integration/convert-project-wizard.md
@@ -47,9 +47,9 @@ You have successfully enabled the Progress&reg; Telerik&reg; UI for Blazor compo
 There are a few common problems that might occur when converting a project:
 
 
-* [_Imports.razor not found](#_importsrazor-not-found)
-* [MainLayout.razor not found](#mainlayoutrazor-not-found)
-* [_Host.cshtml or index.html is malformed, doesn't exist, or doesn't contain a head element](#_hostcshtml-or-indexhtml-is-malformed-doesnt-exist-or-doesnt-contain-a-head-element)
+* [_Imports.razor not found](#_imports-razor-not-found)
+* [MainLayout.razor not found](#mainlayout-razor-not-found)
+* [_Host.cshtml or index.html is malformed, doesn't exist, or doesn't contain a head element](#_host-cshtml-or-index-html-is-malformed-doesn-t-exist-or-doesn-t-contain-a-head-element)
 * [Unable to locate services collection](#unable-to-locate-services-collection)
 * [No suitable project to convert](#no-suitable-project-to-convert)
 
diff --git a/getting-started/vs-integration/upgrade-wizard.md b/getting-started/vs-integration/upgrade-wizard.md
@@ -23,7 +23,7 @@ The **Upgrade Information** step of the Upgrade Project Wizard describes the fil
 The Telerik Blazor Upgrade Wizard will do the following:
 
 * Update the version of the referenced Blazor NuGet package. It will also update the package source in the solution-based NuGet config file.
-* Update the version of the theme reference, but only when using CDN. Otherwise, [update the theme manually]({%slug getting-started-vs-integration-new-project%}#step-3-configure-additional-project-settings).
+* Update the version of the theme reference, but only when using CDN. Otherwise, [update the theme manually]({%slug getting-started-vs-integration-new-project%}#step-3-select-theme).
 * Update all local script and style and NuGet package references if you upgrade from a Trial to a Dev version.
 * It will add the new keys in the default (English) localization file.
 
diff --git a/installation/nuget.md b/installation/nuget.md
@@ -18,7 +18,7 @@ You can set up the remote Telerik NuGet feed in the following ways:
 
 * [Use Visual Studio](#use-visual-studio)
 * [Use the .NET CLI](#use-the-net-cli)
-* [Edit the Nuget.Config file](#edit-the-nugetconfig-file)
+* [Edit the Nuget.Config file](#edit-the-nuget-config-file)
 
 >tip When working with the .NET CLI or editing the `NuGet.Config` manually, you can use your Telerik account credentials or a [NuGet API Key](#use-nuget-api-key). If you are logging in to telerik.com through single sign-on (SSO), use a [NuGet API Key](#use-nuget-api-key).
 
diff --git a/knowledge-base/chart-crowded-labels.md b/knowledge-base/chart-crowded-labels.md
@@ -31,8 +31,8 @@ You can control how many labels render, their rotation angle and even font in or
 
 You can also skip directly to the examples:
 
-* [Example - Rotate the Chart Labels](#example---rotate-the-chart-labels)
-* [Example - Skip rendering every n-th label](#example---skip-rendering-every-n-th-label)
+* [Example - Rotate the Chart Labels](#example-rotate-the-chart-labels)
+* [Example - Skip rendering every n-th label](#example-skip-rendering-every-n-th-label)
 
 
 The general approach to customize the Chart is to apply settings using nested tags. In the case of the `Labels` the tag is 
diff --git a/knowledge-base/common-validation-error-in-tooltip.md b/knowledge-base/common-validation-error-in-tooltip.md
@@ -31,7 +31,7 @@ Can you please advise me on how to display validation message as tooltip?
 
 This article contains several different ways to implement validation notifications with popups:
 
-* [Telerik Validation Tooltip Component](#telerikvalidationpopup)
+* [Telerik Validation Tooltip Component](#telerikvalidationtooltip)
 * [Telerik Form Component](#telerikform)
 * [Validation Summary in a Popup](#validation-summary-in-a-popup)
 * [Per-Input Validation Popups](#per-input-validation-popups) - it is much easier to use the Telerik components listed above to get this functionality
diff --git a/knowledge-base/dpl-version-conflict-detected-telerik-zip.md b/knowledge-base/dpl-version-conflict-detected-telerik-zip.md
@@ -64,8 +64,8 @@ There are several ways to fix the NuGet conflict errors:
 
 * [Upgrade Telerik UI for Blazor]({%slug upgrade-tutorial%}), if some [newer version is available](https://www.telerik.com/support/whats-new/blazor-ui/release-history).
 * Downgrade Telerik Document Processing to the older version that `Telerik.UI.for.Blazor` expects for `Telerik.Zip`.
-* [Reference the newer version of `Telerik.Zip` explicitly in the project.](#reference-the-telerikzip-package-explicitly)
-* [Reference the newer version of `Telerik.Documents.SpreadsheetStreaming` explicitly in the project.](#reference-the-telerikdocumentsspreadsheetstreaming-package-explicitly)
+* [Reference the newer version of `Telerik.Zip` explicitly in the project.](#reference-the-telerik-zip-package-explicitly)
+* [Reference the newer version of `Telerik.Documents.SpreadsheetStreaming` explicitly in the project.](#reference-the-telerik-documents-spreadsheetstreaming-package-explicitly)
 
 The ultimate goal is all Telerik NuGet packages in the app to use the same version of `Telerik.Zip`.
 
diff --git a/styling-and-themes/overview.md b/styling-and-themes/overview.md
@@ -104,7 +104,7 @@ The `Telerik.UI.for.Blazor` NuGet package includes only the *Main* swatch of eac
 
 The Telerik themes are decoupled from the Telerik Blazor components, which leads to the following usage requirements:
 
-* When using a CSS theme as local file in `wwwroot`, [replace the file every time you change the Telerik UI for Blazor version]({%slug upgrade-tutorial%}). This includes apps [created with the Telerik Blazor Visual Studio extension without CDN support]({%slug getting-started-vs-integration-new-project%}#step-3-configure-additional-project-settings).
+* When using a CSS theme as local file in `wwwroot`, [replace the file every time you change the Telerik UI for Blazor version]({%slug upgrade-tutorial%}). This includes apps [created with the Telerik Blazor Visual Studio extension without CDN support]({%slug getting-started-vs-integration-new-project%}#step-3-select-theme).
 * When loading <a href="https://www.telerik.com/design-system/docs/themes/kendo-themes/default/swatches/" target="_blank">theme swatches</a> from a CDN, make sure that the theme version is compatible with the Telerik UI for Blazor version. Our [release notes](https://www.telerik.com/support/whats-new/blazor-ui/release-history) provide theme compatibility information for each components version. You can also use a <a href="https://www.telerik.com/design-system/docs/themes/get-started/changelog/" target="_blank">newer minor theme version</a>, which doesn't contain breaking changes. In other words, the latest major theme version may be still incompatible with the latest version of Telerik UI for Blazor.
 
 
