From a00fab3b72e1e6f36b0ca9c50292a479f19567c5 Mon Sep 17 00:00:00 2001 From: Steven Kirk Date: Fri, 14 Oct 2016 13:10:39 +0200 Subject: [PATCH] Wording tweaks. --- docs/spec/binding-from-code.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/spec/binding-from-code.md b/docs/spec/binding-from-code.md index aa7893762b..76f3aa55c9 100644 --- a/docs/spec/binding-from-code.md +++ b/docs/spec/binding-from-code.md @@ -24,8 +24,8 @@ source.OnNext("world!"); ## Binding priorities -You can also pass a priority to a binding. *Note: Priorities only apply to styled properties: they -are ignored for direct properties.* +You can also pass a priority to a binding. *Note: Priorities only apply to styled properties: they* +*are ignored for direct properties.* The priority is passed using the `BindingPriority` enum, which looks like this: @@ -126,7 +126,7 @@ var textBlock = new TextBlock # Using XAML bindings from code -Sometimes when you want the additional features that XAML bindings provide, it's easier to use XAML bindings from code,. For example, using observables you could bind to a property on `DataContext` like this: +Sometimes when you want the additional features that XAML bindings provide, it's easier to use XAML bindings from code. For example, using only observables you could bind to a property on `DataContext` like this: ```csharp var textBlock = new TextBlock(); @@ -136,7 +136,7 @@ var viewModelProperty = textBlock.GetObservable(TextBlock.DataContext) textBlock.Bind(TextBlock, viewModelProperty); ``` -However, it might be preferable to just use a XAML binding in this case: +However, it might be preferable to use a XAML binding in this case: ```csharp var textBlock = new TextBlock