From 4bde4cb0245f05cc8575da9f6edbe01b39383568 Mon Sep 17 00:00:00 2001 From: crisbeto Date: Fri, 15 May 2020 19:49:43 +0200 Subject: [PATCH] build: fix wrong anchors in docs Fixes a failure in the docs generation task due to a couple of wrong links. --- guides/v9-hammerjs-migration.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/guides/v9-hammerjs-migration.md b/guides/v9-hammerjs-migration.md index ccac8c438903..77fd728c23df 100644 --- a/guides/v9-hammerjs-migration.md +++ b/guides/v9-hammerjs-migration.md @@ -36,7 +36,7 @@ by default in Angular versions 8 and below. If your application provides a custom [`HAMMER_GESTURE_CONFIG`][1] and also references the deprecated Angular Material `GestureConfig`, the migration will print a warning about ambiguous usage. The migration cannot migrate your project automatically and manual changes -are required. Read more [in the dedicated section](#The-migration-reported-ambiguous-usage-What-should-I-do). +are required. Read more [in the dedicated section](#the-migration-reported-ambiguous-usage-what-should-i-do). ### How does the schematic remove HammerJS? @@ -62,12 +62,12 @@ import 'hammerjs'; The migration cannot automatically remove HammerJS from tests. Please manually clean up the test setup and resolve any test issues. Read more in a -[dedicated section for test migration](#How-to-migrate-my-tests). +[dedicated section for test migration](#how-to-migrate-my-tests). ### How do I migrate references to the deprecated `GestureConfig`? The `GestureConfig` can be consumed in multiple ways. The migration covers the most common cases. -The most common case is that an `NgModule` in your application directly provides `GestureConfig`: +The most common case is that an `NgModule` in your application directly provides `GestureConfig`: ```typescript import {GestureConfig} from '@angular/material/core';