Skip to content

Commit 168db86

Browse files
nschonnimairaw
authored andcommitted
typo: hander -> handler (#2155)
1 parent a81ad28 commit 168db86

File tree

9 files changed

+13
-13
lines changed

9 files changed

+13
-13
lines changed

xml/System.Activities.Tracking/FaultPropagationQuery.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@
5959
<ReturnType>System.String</ReturnType>
6060
</ReturnValue>
6161
<Docs>
62-
<summary>Gets the name of the fault hander activity that propagated the fault.</summary>
62+
<summary>Gets the name of the fault handler activity that propagated the fault.</summary>
6363
<value>The activity name.</value>
6464
<remarks>
6565
<format type="text/markdown"><![CDATA[

xml/System.ComponentModel.Design/EventBindingService.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@
137137
<format type="text/markdown"><![CDATA[
138138
139139
## Remarks
140-
Some implementations may intend to remove the event hander when no events are using it. By overriding <xref:System.ComponentModel.Design.EventBindingService.UseMethod%2A> and <xref:System.ComponentModel.Design.EventBindingService.FreeMethod%2A>, an implementation can infer when a method is no longer needed.
140+
Some implementations may intend to remove the event handler when no events are using it. By overriding <xref:System.ComponentModel.Design.EventBindingService.UseMethod%2A> and <xref:System.ComponentModel.Design.EventBindingService.FreeMethod%2A>, an implementation can infer when a method is no longer needed.
141141
142142
]]></format>
143143
</remarks>
@@ -630,7 +630,7 @@
630630
<format type="text/markdown"><![CDATA[
631631
632632
## Remarks
633-
Some implementations may intend to remove the event hander when no events are using it. By overriding <xref:System.ComponentModel.Design.EventBindingService.UseMethod%2A> and <xref:System.ComponentModel.Design.EventBindingService.FreeMethod%2A>, an implementation can infer when a method is no longer needed.
633+
Some implementations may intend to remove the event handler when no events are using it. By overriding <xref:System.ComponentModel.Design.EventBindingService.UseMethod%2A> and <xref:System.ComponentModel.Design.EventBindingService.FreeMethod%2A>, an implementation can infer when a method is no longer needed.
634634
635635
]]></format>
636636
</remarks>

xml/System.Reflection/EventInfo.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -179,7 +179,7 @@
179179
180180
Each time the event is raised by the target parameter, the method or methods encapsulated by the handler are invoked.
181181
182-
You might use the `AddEventHander` method when you load a type after the program is already compiled, when it is not possible to use the C# += syntax or the Visual Basic `WithEvents` and `Handles` keywords to hook up the event.
182+
You might use the `AddEventHandler` method when you load a type after the program is already compiled, when it is not possible to use the C# += syntax or the Visual Basic `WithEvents` and `Handles` keywords to hook up the event.
183183
184184
## Examples
185185
The following example creates an instance of the <xref:System.Timers.Timer?displayProperty=nameWithType> class, creates an event handler using a dynamic assembly, and hooks up the dynamic event handler. All actions are performed using late binding.

xml/System.Speech.Recognition/SpeechRecognitionEngine.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1719,7 +1719,7 @@ namespace SreEmulateRecognizeAsync
17191719
SpeechRecognizedHandler);
17201720
recognizer.EmulateRecognizeCompleted +=
17211721
new EventHandler<EmulateRecognizeCompletedEventArgs>(
1722-
EmulateRecognizeCompletedHander);
1722+
EmulateRecognizeCompletedHandler);
17231723
17241724
// Start four asynchronous emulated recognition operations.
17251725
TestRecognizeAsync(recognizer, "Smith");
@@ -1826,7 +1826,7 @@ namespace SreEmulateRecognizeAsync
18261826
}
18271827
}
18281828
1829-
static void EmulateRecognizeCompletedHander(
1829+
static void EmulateRecognizeCompletedHandler(
18301830
object sender, EmulateRecognizeCompletedEventArgs e)
18311831
{
18321832
Console.WriteLine(" EmulateRecognizeCompleted event raised.");

xml/System.Web/IHttpAsyncHandler.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@
2222
<format type="text/markdown"><![CDATA[
2323
2424
## Remarks
25-
An <xref:System.Web.IHttpAsyncHandler> class can be associated with a file name extension or a particular URL by a configuration file, in the `httpHandlers` configuration section. The ASP.NET infrastructure will then instantiate and call the handler when the corresponding request is received. Alternatively, the handler can be defined in an .ashx file and when the corresponding request is received for the .ashx file the hander will be executed.
25+
An <xref:System.Web.IHttpAsyncHandler> class can be associated with a file name extension or a particular URL by a configuration file, in the `httpHandlers` configuration section. The ASP.NET infrastructure will then instantiate and call the handler when the corresponding request is received. Alternatively, the handler can be defined in an .ashx file and when the corresponding request is received for the .ashx file the handler will be executed.
2626
2727
]]></format>
2828
</remarks>

xml/System.Windows.Input/ExecutedRoutedEventArgs.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -76,8 +76,8 @@
7676
## Examples
7777
The following example creates an <xref:System.Windows.Input.ExecutedRoutedEventHandler> that handles multiple commands. The handler checks the <xref:System.Windows.Input.ExecutedRoutedEventArgs.Command%2A> property on the <xref:System.Windows.Input.ExecutedRoutedEventArgs> to determine which method to call.
7878
79-
[!code-csharp[commandingoverviewsnippets#CommandingOverviewMultipleCmdHander](~/samples/snippets/csharp/VS_Snippets_Wpf/CommandingOverviewSnippets/CSharp/Window1.xaml.cs#commandingoverviewmultiplecmdhander)]
80-
[!code-vb[commandingoverviewsnippets#CommandingOverviewMultipleCmdHander](~/samples/snippets/visualbasic/VS_Snippets_Wpf/CommandingOverviewSnippets/visualbasic/window1.xaml.vb#commandingoverviewmultiplecmdhander)]
79+
[!code-csharp[commandingoverviewsnippets#CommandingOverviewMultipleCmdHandler](~/samples/snippets/csharp/VS_Snippets_Wpf/CommandingOverviewSnippets/CSharp/Window1.xaml.cs#commandingoverviewmultiplecmdhandler)]
80+
[!code-vb[commandingoverviewsnippets#CommandingOverviewMultipleCmdHandler](~/samples/snippets/visualbasic/VS_Snippets_Wpf/CommandingOverviewSnippets/visualbasic/window1.xaml.vb#commandingoverviewmultiplecmdhandler)]
8181
8282
]]></format>
8383
</remarks>

xml/System.Windows.Media.Animation/Clock.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -285,7 +285,7 @@
285285
A clock that is <xref:System.Windows.Media.Animation.ClockState.Filling> has a <xref:System.Windows.Media.Animation.Clock.CurrentProgress%2A> of 1.0.
286286
287287
## Using a Timeline as a Timer
288-
A timeline's clock will only progress when there's an event hander associated with it or (in the case of an <xref:System.Windows.Media.Animation.AnimationClock> object) it is associated with a property. For this reason (and others), it's not recommended that you use a <xref:System.Windows.Media.Animation.Timeline> as a timer.
288+
A timeline's clock will only progress when there's an event handler associated with it or (in the case of an <xref:System.Windows.Media.Animation.AnimationClock> object) it is associated with a property. For this reason (and others), it's not recommended that you use a <xref:System.Windows.Media.Animation.Timeline> as a timer.
289289
290290
]]></format>
291291
</remarks>
@@ -400,7 +400,7 @@
400400
## Remarks
401401
402402
## Using a Timeline as a Timer
403-
A timeline's clock will only progress when there's an event hander associated with it or (in the case of an <xref:System.Windows.Media.Animation.AnimationClock> object) it is associated with a property. For this reason (and others), it's not recommended that you use a <xref:System.Windows.Media.Animation.Timeline> as a timer.
403+
A timeline's clock will only progress when there's an event handler associated with it or (in the case of an <xref:System.Windows.Media.Animation.AnimationClock> object) it is associated with a property. For this reason (and others), it's not recommended that you use a <xref:System.Windows.Media.Animation.Timeline> as a timer.
404404
405405
]]></format>
406406
</remarks>

xml/System.Windows.Media.Animation/Timeline.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@
5858
For an example of a data bound animation, see the [Key Spline Animation Sample](https://go.microsoft.com/fwlink/?LinkID=160011) .
5959
6060
## Using a Timeline as a Timer
61-
A timeline's clock will only progress when there's an event hander associated with it or (in the case of an <xref:System.Windows.Media.Animation.AnimationClock> object) it is associated with a property. For this reason (and others), it's not recommended that you use a <xref:System.Windows.Media.Animation.Timeline> as a timer.
61+
A timeline's clock will only progress when there's an event handler associated with it or (in the case of an <xref:System.Windows.Media.Animation.AnimationClock> object) it is associated with a property. For this reason (and others), it's not recommended that you use a <xref:System.Windows.Media.Animation.Timeline> as a timer.
6262
6363
]]></format>
6464
</remarks>

xml/System.Windows/PresentationSource.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@
100100
</Parameters>
101101
<Docs>
102102
<param name="element">The element to add the handler to.</param>
103-
<param name="handler">The hander implementation to add.</param>
103+
<param name="handler">The handler implementation to add.</param>
104104
<summary>Adds a handler for the <see langword="SourceChanged" /> event to the provided element.</summary>
105105
<remarks>
106106
<format type="text/markdown"><![CDATA[

0 commit comments

Comments
 (0)