Xamarin.Forms bookmark fixes (#1701)

* Removed custom bookmarks.

* no-loc key error fixed.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* XAML bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fix.

* Bookmark fix.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

* Bookmark fixes.

Author: davidbritch

docs/get-started/tutorials/image/includes/customize-appearance.md

@@ -12,7 +12,7 @@
 
     This code sets the [`Aspect`](xref:Xamarin.Forms.Image.Aspect) property, which defines the scaling mode of the image, to [`Fill`](xref:Xamarin.Forms.Aspect.Fill). The `Fill` member is defined in the [`Aspect`](xref:Xamarin.Forms.Aspect) enumeration, and stretches the image to completely fill the view, regardless of whether the image is distorted. For more information about image scaling, see [Displaying images](~/xamarin-forms/user-interface/images.md#display-images) in the [Images in Xamarin.Forms](~/xamarin-forms/user-interface/images.md) guide.
 
-    The `OnPlatform` markup extension enables you to customize UI appearance on a per-platform basis. In this example, the markup extension is used to set the [`HeightRequest`](xref:Xamarin.Forms.VisualElement.HeightRequest) and [`WidthRequest`](xref:Xamarin.Forms.VisualElement.WidthRequest) properties to 300 device-independent units on iOS and to 250 device-independent units on Android. For more information about the `OnPlatform` markup extension, see [OnPlatform markup extension](~/xamarin-forms/xaml/markup-extensions/consuming.md#onplatform) in the [Consuming XAML Markup Extensions](~/xamarin-forms/xaml/markup-extensions/consuming.md) guide.
+    The `OnPlatform` markup extension enables you to customize UI appearance on a per-platform basis. In this example, the markup extension is used to set the [`HeightRequest`](xref:Xamarin.Forms.VisualElement.HeightRequest) and [`WidthRequest`](xref:Xamarin.Forms.VisualElement.WidthRequest) properties to 300 device-independent units on iOS and to 250 device-independent units on Android. For more information about the `OnPlatform` markup extension, see [OnPlatform markup extension](~/xamarin-forms/xaml/markup-extensions/consuming.md#onplatform-markup-extension) in the [Consuming XAML Markup Extensions](~/xamarin-forms/xaml/markup-extensions/consuming.md) guide.
 
     In addition, the [`HorizontalOptions`](xref:Xamarin.Forms.View.HorizontalOptions) property specifies that the image will be horizontally centered.
 
@@ -34,7 +34,7 @@
 
     This code sets the [`Aspect`](xref:Xamarin.Forms.Image.Aspect) property, which defines the scaling mode of the image, to [`Fill`](xref:Xamarin.Forms.Aspect.Fill). The `Fill` member is defined in the [`Aspect`](xref:Xamarin.Forms.Aspect) enumeration, and stretches the image to completely fill the view, regardless of whether the image is distorted. For more information about image scaling, see [Displaying images](~/xamarin-forms/user-interface/images.md#display-images) in the [Images in Xamarin.Forms](~/xamarin-forms/user-interface/images.md) guide.
 
-    The `OnPlatform` markup extension enables you to customize UI appearance on a per-platform basis. In this example, the markup extension is used to set the [`HeightRequest`](xref:Xamarin.Forms.VisualElement.HeightRequest) and [`WidthRequest`](xref:Xamarin.Forms.VisualElement.WidthRequest) properties to 300 on iOS and to 250 on Android. For more information about the `OnPlatform` markup extension, see [OnPlatform markup extension](~/xamarin-forms/xaml/markup-extensions/consuming.md#onplatform) in the [Consuming XAML Markup Extensions](~/xamarin-forms/xaml/markup-extensions/consuming.md) guide.
+    The `OnPlatform` markup extension enables you to customize UI appearance on a per-platform basis. In this example, the markup extension is used to set the [`HeightRequest`](xref:Xamarin.Forms.VisualElement.HeightRequest) and [`WidthRequest`](xref:Xamarin.Forms.VisualElement.WidthRequest) properties to 300 on iOS and to 250 on Android. For more information about the `OnPlatform` markup extension, see [OnPlatform markup extension](~/xamarin-forms/xaml/markup-extensions/consuming.md#onplatform-markup-extension) in the [Consuming XAML Markup Extensions](~/xamarin-forms/xaml/markup-extensions/consuming.md) guide.
 
     In addition, the [`HorizontalOptions`](xref:Xamarin.Forms.View.HorizontalOptions) property specifies that the image will be horizontally centered.
 

docs/ios/user-interface/ios-ui/introduction-to-the-appearance-api.md

@@ -81,7 +81,7 @@ progress2.TrackTintColor = UIColor.FromRGB (197,255,132);
 ## Using UIAppearance in Xamarin.Forms
 
 The Appearance API can be useful when
-[styling the iOS app](~/xamarin-forms/platform/ios/formatting.md#uiappearance)
+[styling the iOS app](~/xamarin-forms/platform/ios/formatting.md#uiappearance-api)
 in Xamarin.Forms solutions. A few lines in the `AppDelegate` class can help
 to implement a specific color scheme without having to create a
 [custom renderer](~/xamarin-forms/app-fundamentals/custom-renderer/index.md).
@@ -130,4 +130,4 @@ Refer to the [Introduction to the Appearance API](~/ios/user-interface/ios-ui/in
 
 - [Appearance (sample)](https://docs.microsoft.com/samples/xamarin/ios-samples/appearance)
 - [UIAppearance Protocol Reference](https://developer.apple.com/library/ios/documentation/UIKit/Reference/UIAppearance_Protocol/)
-- [Appearance in Xamarin.Forms](~/xamarin-forms/platform/ios/formatting.md#uiappearance)
+- [Appearance in Xamarin.Forms](~/xamarin-forms/platform/ios/formatting.md#uiappearance-api)

docs/xamarin-forms/app-fundamentals/accessibility/automation-properties.md

@@ -18,10 +18,10 @@ _Xamarin.Forms allows accessibility values to be set on user interface elements
 
 Xamarin.Forms allows automation properties to be set on user interface elements via the following attached properties:
 
-- `AutomationProperties.IsInAccessibleTree` – indicates whether the element is available to an accessible application. For more information, see [AutomationProperties.IsInAccessibleTree](#isinaccessibletree).
-- `AutomationProperties.Name` – a short description of the element that serves as a speakable identifier for the element. For more information, see [AutomationProperties.Name](#name).
-- `AutomationProperties.HelpText` – a longer description of the element, which can be thought of as tooltip text associated with the element. For more information, see [AutomationProperties.HelpText](#helptext).
-- `AutomationProperties.LabeledBy` – allows another element to define accessibility information for the current element. For more information, see [AutomationProperties.LabeledBy](#labeledby).
+- `AutomationProperties.IsInAccessibleTree` – indicates whether the element is available to an accessible application. For more information, see [AutomationProperties.IsInAccessibleTree](#automationpropertiesisinaccessibletree).
+- `AutomationProperties.Name` – a short description of the element that serves as a speakable identifier for the element. For more information, see [AutomationProperties.Name](#automationpropertiesname).
+- `AutomationProperties.HelpText` – a longer description of the element, which can be thought of as tooltip text associated with the element. For more information, see [AutomationProperties.HelpText](#automationpropertieshelptext).
+- `AutomationProperties.LabeledBy` – allows another element to define accessibility information for the current element. For more information, see [AutomationProperties.LabeledBy](#automationpropertieslabeledby).
 
 These attached properties set native accessibility values so that a screen reader can speak about the element. For more information about attached properties, see [Attached Properties](~/xamarin-forms/xaml/attached-properties.md).
 
@@ -44,8 +44,6 @@ Screen readers also read different accessibility values. In the sample applicati
 
 In addition, Narrator will prioritize `AutomationProperties.Name`, `AutomationProperties.LabeledBy`, and then `AutomationProperties.HelpText`. On Android, TalkBack may combine the `AutomationProperties.Name` and `AutomationProperties.HelpText` values. Therefore, it's recommended that thorough accessibility testing is carried out on each platform to ensure an optimal experience.
 
-<a name="isinaccessibletree" />
-
 ## AutomationProperties.IsInAccessibleTree
 
 The `AutomationProperties.IsInAccessibleTree` attached property is a `boolean` that determines if the element is accessible, and hence visible, to screen readers. It must be set to `true` to use the other accessibility attached properties. This can be accomplished in XAML as follows:
@@ -64,8 +62,6 @@ AutomationProperties.SetIsInAccessibleTree(entry, true);
 > [!NOTE]
 > Note that the [`SetValue`](xref:Xamarin.Forms.BindableObject.SetValue(Xamarin.Forms.BindableProperty,System.Object)) method can also be used to set the `AutomationProperties.IsInAccessibleTree` attached property – `entry.SetValue(AutomationProperties.IsInAccessibleTreeProperty, true);`
 
-<a name="name" />
-
 ## AutomationProperties.Name
 
 The `AutomationProperties.Name` attached property value should be a short, descriptive text string that a screen reader uses to announce an element. This property should be set for elements that have a meaning that is important for understanding the content or interacting with the user interface. This can be accomplished in XAML as follows:
@@ -86,8 +82,6 @@ AutomationProperties.SetName(activityIndicator, "Progress indicator");
 > [!NOTE]
 > Note that the [`SetValue`](xref:Xamarin.Forms.BindableObject.SetValue(Xamarin.Forms.BindableProperty,System.Object)) method can also be used to set the `AutomationProperties.Name` attached property – `activityIndicator.SetValue(AutomationProperties.NameProperty, "Progress indicator");`
 
-<a name="helptext" />
-
 ## AutomationProperties.HelpText
 
 The `AutomationProperties.HelpText` attached property should be set to text that describes the user interface element, and can be thought of as tooltip text associated with the element. This can be accomplished in XAML as follows:
@@ -111,8 +105,6 @@ AutomationProperties.SetHelpText(button, "Tap to toggle the activity indicator")
 
 On some platforms, for edit controls such as an [`Entry`](xref:Xamarin.Forms.Entry), the `HelpText` property can sometimes be omitted and replaced with placeholder text. For example, "Enter your name here" is a good candidate for the [`Entry.Placeholder`](xref:Xamarin.Forms.InputView.Placeholder) property that places the text in the control prior to the user's actual input.
 
-<a name="labeledby" />
-
 ## AutomationProperties.LabeledBy
 
 The `AutomationProperties.LabeledBy` attached property allows another element to define accessibility information for the current element. For example, a [`Label`](xref:Xamarin.Forms.Label) next to an [`Entry`](xref:Xamarin.Forms.Entry) can be used to describe what the `Entry` represents. This can be accomplished in XAML as follows:

docs/xamarin-forms/app-fundamentals/app-lifecycle.md

@@ -14,11 +14,9 @@ no-loc: [Xamarin.Forms, Xamarin.Essentials]
 
 The [`Application`](xref:Xamarin.Forms.Application) base class provides the following features:
 
-- [Lifecycle methods](#Lifecycle_Methods) `OnStart`, `OnSleep`, and `OnResume`.
-- [Page navigation events](#page) [`PageAppearing`](xref:Xamarin.Forms.Application.PageAppearing), [`PageDisappearing`](xref:Xamarin.Forms.Application.PageDisappearing).
-- [Modal navigation events](#modal) `ModalPushing`, `ModalPushed`, `ModalPopping`, and `ModalPopped`.
-
-<a name="Lifecycle_Methods" />
+- [Lifecycle methods](#lifecycle-methods) `OnStart`, `OnSleep`, and `OnResume`.
+- [Page navigation events](#page-navigation-events) [`PageAppearing`](xref:Xamarin.Forms.Application.PageAppearing), [`PageDisappearing`](xref:Xamarin.Forms.Application.PageDisappearing).
+- [Modal navigation events](#modal-navigation-events) `ModalPushing`, `ModalPushed`, `ModalPopping`, and `ModalPopped`.
 
 ## Lifecycle methods
 
@@ -51,9 +49,7 @@ protected override void OnResume()
 > [!IMPORTANT]
 > On Android, the `OnStart` method will be called on rotation as well as when the application first starts, if the main activity lacks `ConfigurationChanges = ConfigChanges.ScreenSize | ConfigChanges.Orientation` in the `[Activity()]` attribute.
 
-<a name="page" />
-
-## Page notification events
+## Page navigation events
 
 There are two events on the [`Application`](xref:Xamarin.Forms.Application) class that provide notification of pages appearing and disappearing:
 
@@ -65,8 +61,6 @@ These events can be used in scenarios where you want to track pages as they appe
 > [!NOTE]
 > The [`PageAppearing`](xref:Xamarin.Forms.Application.PageAppearing) and [`PageDisappearing`](xref:Xamarin.Forms.Application.PageDisappearing) events are raised from the [`Page`](xref:Xamarin.Forms.Page) base class immediately after the [`Page.Appearing`](xref:Xamarin.Forms.Page.Appearing) and [`Page.Disappearing`](xref:Xamarin.Forms.Page.Disappearing) events, respectively.
 
-<a name="modal" />
-
 ## Modal navigation events
 
 There are four events on the [`Application`](xref:Xamarin.Forms.Application) class, each with their own event arguments, that let you respond to modal pages being shown and dismissed:

docs/xamarin-forms/app-fundamentals/application-class.md

@@ -16,7 +16,7 @@ no-loc: [Xamarin.Forms, Xamarin.Essentials]
 The `Application` base class offers the following features, which are exposed in your projects default `App` subclass:
 
 * A `MainPage` property, which is where to set the initial page for the app.
-* A persistent [`Properties` dictionary](#Properties_Dictionary) to store simple values across lifecycle state changes.
+* A persistent [`Properties` dictionary](#properties-dictionary) to store simple values across lifecycle state changes.
 * A static `Current` property that contains a reference to the current application object.
 
 It also exposes [Lifecycle methods](~/xamarin-forms/app-fundamentals/app-lifecycle.md) such
@@ -72,8 +72,6 @@ public class App : Xamarin.Forms.Application
 }
 ```
 
-<a name="Properties_Dictionary" />
-
 ## Properties dictionary
 
 The `Application` subclass has a static `Properties` dictionary which can be used to store data, in particular for use in the `OnStart`, `OnSleep`, and `OnResume` methods. This can be accessed from anywhere in your Xamarin.Forms code using `Application.Current.Properties`.

docs/xamarin-forms/app-fundamentals/custom-renderer/contentpage.md

@@ -24,14 +24,12 @@ The following diagram illustrates the relationship between the [`ContentPage`](x
 
 The rendering process can be taken advantage of to implement platform-specific customizations by creating a custom renderer for a [`ContentPage`](xref:Xamarin.Forms.ContentPage) on each platform. The process for doing this is as follows:
 
-1. [Create](#Creating_the_Xamarin.Forms_Page) a Xamarin.Forms page.
-1. [Consume](#Consuming_the_Xamarin.Forms_Page) the page from Xamarin.Forms.
-1. [Create](#Creating_the_Page_Renderer_on_each_Platform) the custom renderer for the page on each platform.
+1. [Create](#creating-the-xamarinforms-page) a Xamarin.Forms page.
+1. [Consume](#consuming-the-xamarinforms-page) the page from Xamarin.Forms.
+1. [Create](#creating-the-page-renderer-on-each-platform) the custom renderer for the page on each platform.
 
 Each item will now be discussed in turn, to implement a `CameraPage` that provides a live camera feed and the ability to capture a photo.
 
-<a name="Creating_the_Xamarin.Forms_Page" />
-
 ## Creating the Xamarin.Forms Page
 
 An unaltered [`ContentPage`](xref:Xamarin.Forms.ContentPage) can be added to the shared Xamarin.Forms project, as shown in the following XAML code example:
@@ -71,8 +69,6 @@ public class CameraPageCS : ContentPage
 
 An instance of the `CameraPage` will be used to display the live camera feed on each platform. Customization of the control will be carried out in the custom renderer, so no additional implementation is required in the `CameraPage` class.
 
-<a name="Consuming_the_Xamarin.Forms_Page" />
-
 ## Consuming the Xamarin.Forms Page
 
 The empty `CameraPage` must be displayed by the Xamarin.Forms application. This occurs when a button on the `MainPage` instance is tapped, which in turn executes the `OnTakePhotoButtonClicked` method, as shown in the following code example:
@@ -86,8 +82,6 @@ async void OnTakePhotoButtonClicked (object sender, EventArgs e)
 
 This code simply navigates to the `CameraPage`, on which custom renderers will customize the page's appearance on each platform.
 
-<a name="Creating_the_Page_Renderer_on_each_Platform" />
-
 ## Creating the Page Renderer on each Platform
 
 The process for creating the custom renderer class is as follows:

docs/xamarin-forms/app-fundamentals/custom-renderer/entry.md

@@ -24,17 +24,15 @@ The following diagram illustrates the relationship between the [`Entry`](xref:Xa
 
 The rendering process can be taken advantage of to implement platform-specific customizations by creating a custom renderer for the [`Entry`](xref:Xamarin.Forms.Entry) control on each platform. The process for doing this is as follows:
 
-1. [Create](#Creating_the_Custom_Entry_Control) a Xamarin.Forms custom control.
-1. [Consume](#Consuming_the_Custom_Control) the custom control from Xamarin.Forms.
-1. [Create](#Creating_the_Custom_Renderer_on_each_Platform) the custom renderer for the control on each platform.
+1. [Create](#creating-the-custom-entry-control) a Xamarin.Forms custom control.
+1. [Consume](#consuming-the-custom-control) the custom control from Xamarin.Forms.
+1. [Create](#creating-the-custom-renderer-on-each-platform) the custom renderer for the control on each platform.
 
 Each item will now be discussed in turn, to implement an [`Entry`](xref:Xamarin.Forms.Entry) control that has a different background color on each platform.
 
 > [!IMPORTANT]
 > This article explains how to create a simple custom renderer. However, it's not necessary to create a custom renderer to implement an `Entry` that has a different background color on each platform. This can be more easily accomplished by using the [`Device`](xref:Xamarin.Forms.Device) class, or the `OnPlatform` markup extension, to provide platform-specific values. For more information, see [Providing Platform-Specific Values](~/xamarin-forms/platform/device.md#provide-platform-specific-values) and [OnPlatform Markup Extension](~/xamarin-forms/xaml/markup-extensions/consuming.md#onplatform-markup-extension).
 
-<a name="Creating_the_Custom_Entry_Control"></a>
-
 ## Creating the Custom Entry Control
 
 A custom [`Entry`](xref:Xamarin.Forms.Entry) control can be created by subclassing the `Entry` control, as shown in the following code example:
@@ -47,8 +45,6 @@ public class MyEntry : Entry
 
 The `MyEntry` control is created in the .NET Standard library project and is simply an [`Entry`](xref:Xamarin.Forms.Entry) control. Customization of the control will be carried out in the custom renderer, so no additional implementation is required in the `MyEntry` control.
 
-<a name="Consuming_the_Custom_Control"></a>
-
 ## Consuming the Custom Control
 
 The `MyEntry` control can be referenced in XAML in the .NET Standard library project by declaring a namespace for its location and using the namespace prefix on the control element. The following code example shows how the `MyEntry` control can be consumed by a XAML page:
@@ -92,8 +88,6 @@ This code instantiates a new [`ContentPage`](xref:Xamarin.Forms.ContentPage) obj
 
 A custom renderer can now be added to each application project to customize the control's appearance on each platform.
 
-<a name="Creating_the_Custom_Renderer_on_each_Platform"></a>
-
 ## Creating the Custom Renderer on each Platform
 
 The process for creating the custom renderer class is as follows: