From f8f6e8d079116d88cd204ea3c5d1f04bec0a9d6f Mon Sep 17 00:00:00 2001 From: Steven Kirk Date: Tue, 5 Jul 2016 20:12:56 +0200 Subject: [PATCH] Clarified documentation. --- src/Markup/Avalonia.Markup.Xaml/Data/DelayedBinding.cs | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/Markup/Avalonia.Markup.Xaml/Data/DelayedBinding.cs b/src/Markup/Avalonia.Markup.Xaml/Data/DelayedBinding.cs index ea79c7429f..083cb24b11 100644 --- a/src/Markup/Avalonia.Markup.Xaml/Data/DelayedBinding.cs +++ b/src/Markup/Avalonia.Markup.Xaml/Data/DelayedBinding.cs @@ -14,11 +14,11 @@ namespace Avalonia.Markup.Xaml.Data /// /// /// The XAML engine applies its bindings in a delayed manner where bindings are only applied - /// when a control has finished initializing. This was done because applying bindings as soon + /// when a control has finished initializing. This is done because applying bindings as soon /// as controls are created means that long-form bindings (i.e. bindings that don't use the - /// `{Binding}` markup extension) don't work as the binding is applied to the property before - /// the binding properties are set, and looking at WPF it uses a similar mechanism for bindings - /// that come from XAML. + /// `{Binding}` markup extension but instead use `<Binding>`) don't work, as the binding + /// is applied to the property before the properties on the `Binding` object are set. Looking + /// at WPF it uses a similar mechanism for bindings that come from XAML. /// public static class DelayedBinding {