Updates multiple docs

Author: egil

docs/samples/tests/razor/ClickMeTest.razor

@@ -0,0 +1,19 @@
+@code
+{
+  [Fact]
+  public void Test()
+  {
+    // Arrange
+    using var ctx = new TestContext();
+    var cut = ctx.Render(@<ClickMe />);
+    var buttonElement = cut.Find("button");
+
+    // Act
+    buttonElement.Click();
+    buttonElement.Click(detail: 3, ctrlKey: true);
+    buttonElement.Click(new MouseEventArgs());
+
+    // Assert
+    // ...
+  }
+}

docs/samples/tests/xunit/ClickMeTest.cs

@@ -7,7 +7,7 @@ namespace Bunit.Docs.Samples
   public class ClickMeTest
   {
     [Fact]
-    public void ClickingButtonWorks()
+    public void Test()
     {
       // Arrange
       using var ctx = new TestContext();

docs/site/docs/code-of-conduct.md

@@ -1,11 +1,11 @@
 ---
 uid: code-of-conduct
-title: Contributor Covenant Code of Conduct
+title: Contributor covenant code of conduct
 ---
 
-# Contributor Covenant Code of Conduct 
+# Contributor covenant code of conduct 
 
-## Our Pledge
+## Our pledge
 
 In the interests of fostering an open and welcoming environment, we as
 contributors and maintainers pledge to make our project and
@@ -14,7 +14,7 @@ size, disability, ethnicity, sexuality, gender identity and expression,
 level of experience, education, socio-economic status, nationality, personal
 appearance, race, or religion.
 
-## Our Standards
+## Our standards
 
 Examples of behavior that contribute towards creating a positive environment
 include:
@@ -35,7 +35,7 @@ Examples of unacceptable behavior by participants include:
 * Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
-## Our Responsibilities
+## Our responsibilities
 
 Project maintainers are responsible for clarifying the standards of acceptable
 behavior and are expected to take appropriate and fair corrective action in

docs/site/docs/contribute.md

@@ -3,17 +3,17 @@ uid: contribute
 title: Contribute
 ---
 
-# How to Contribute
+# How to contribute
 
 One of the easiest ways to contribute is to participate in discussions on GitHub issues. You can also contribute by submitting pull requests with code changes.
 
-## General Feedback and Discussions
+## General feedback and discussions
 Start a discussion on the [bUnit discussion list](https://github.com/egil/bUnit/discussions).
 
-## Bugs and Feature Requests
+## Bugs and feature requests
 For bugs or feature requests, log a new issue on the [issues list](https://github.com/egil/bunit/issues). Be sure to use the right template.
 
-## Contributing Code and Content
+## Contributing code and content
 
 bUnit accepts fixes and features. Here is what you should do when writing code for bUnit:
 
@@ -28,18 +28,18 @@ Here are some resources to help you get started on how to contribute code or new
 * ["Help wanted" issues](https://github.com/egil/bunit/labels/help%20wanted) - these issues are up for grabs if you want to create a fix. To do this, simply comment on the issue you want to fix.
 * ["Good first issue" issues](https://github.com/egil/bunit/labels/good%20first%20issue) - these are good for newcomers. Good first issues are small, usually require just a few hours of work, and do not require a deep technical knowledge of bUnit. This is a good place to start if you want to become familiar with bUnit’s inner workings and maybe take on bigger issues later.
 
-### Identifying the Scale of a Contribution
+### Identifying the scale of a contribution
 
 If you would like to contribute to bUnit, first identify the scale of what you would like to contribute. If it is small (grammar/spelling or a bug fix), feel free to start working on a fix. If you are submitting a feature or substantial code contribution, please discuss it with us first. 
 
 You might also read these two blogs posts on contributing code: [Open Source Contribution Etiquette](http://tirania.org/blog/archive/2010/Dec-31.html) by Miguel de Icaza and [Don't "Push" Your Pull Requests](https://www.igvita.com/2011/12/19/dont-push-your-pull-requests/) by Ilya Grigorik. These blog posts highlight good open source collaboration etiquette and help align expectations between you and us.
 
 All code submissions will be rigorously reviewed and tested, and only those that meet a high bar for both quality and design/roadmap appropriateness will be merged into the source.
 
-### Submitting a Pull Request
+### Submitting a pull request
 
 If you don't know what a pull request is, read this article: https://help.github.com/articles/using-pull-requests. Make sure the repository can build and all tests pass. It is also a good idea to familiarize yourself with the project workflow and our coding conventions.
 
-## Code of Conduct
+## Code of conduct
 
 See <xref:code-of-conduct>

docs/site/docs/external-resources.md

@@ -6,13 +6,11 @@ title: External Resources
 # Presentations, guides, articles, tutorials, and blog posts
 Here is a list of some web content that covers bUnit. If you produce something you think can be useful to bUnit's users, feel free to add it to this page and send a pull request.
 
-### Presentations
-
-- **[Testing Blazor Components - session from .NET Conf - Focus on Blazor](https://youtu.be/5d-uIxx1cUE)**  
-  Content is based on beta-5.1 of bUnit.
-
 ### Podcasts/Twitch/YouTube/Live coding
 
+- **[Test Driving the Blazing Pizza Workshop with bUnit (multiple videos)](https://youtube.com/playlist?list=PL2LoDmbC1g20uJjUwPGQxpQjdnmpMqV0t)**  
+  Content is based on 1.0.0 of bUnit.
+
 - **[.NET Rocks! - Testing Blazor Apps with Egil Hansen](https://www.dotnetrocks.com/?show=1690)**  
   Content is based on beta-7 of bUnit.  
 
@@ -21,7 +19,12 @@ Here is a list of some web content that covers bUnit. If you produce something y
 
 - **[Blazor StateHasChanged: Blazor Component Unit Testing with Egil Hansen](https://www.youtube.com/watch?v=x-zzcwHdZOk&t=211)**   
   Content is based on beta-5.1 of bUnit.
-  
+
+### Presentations
+
+- **[Testing Blazor Components - session from .NET Conf - Focus on Blazor](https://youtu.be/5d-uIxx1cUE)**  
+  Content is based on beta-5.1 of bUnit.
+
 ### Articles and blog posts 
 
 - **[bUnit for Blazor and How to Integrate it in Azure Pipeline](https://www.syncfusion.com/blogs/post/bunit-for-blazor-and-how-to-integrate-it-in-azure-pipeline.aspx) by Ramkumar Shanmugam**   

docs/site/docs/getting-started/index.md

@@ -1,9 +1,9 @@
 ---
 uid: getting-started
-title: Getting Started with bUnit
+title: Getting started with bUnit
 ---
 
-# Getting Started with bUnit
+# Getting started with bUnit
 
 To start writing tests for Blazor components, first set up a test project and then you can start adding tests.
 
@@ -14,10 +14,10 @@ The *basic* getting started topics are as follows:
 
 The *next level* topics are:
 
-1. **[Providing different types of input](xref:providing-input)** to a component under test in C# based tests, e.g. passing parameters or injecting services.
+1. **[Providing different types of input](xref:providing-input)** to a component under test, e.g. passing parameters or injecting services.
 2. **[Verifying output in various ways](xref:verification)** from a component under test, e.g. inspecting the rendered markup.
 3. **[Mocking dependencies](xref:test-doubles)** a component under test has, e.g. the `IJsRuntime` or `HttpClient`.
 
-## Getting Help
+## Getting help
 
 Can't figure out how to write a test for a testing scenario? Do you have a testing scenario that is hard to write or cannot be written elegantly with bUnit? Have you found a bug in bUnit? Head over to [bUnit’s discussion forum](https://github.com/egil/bUnit/discussions) to ask a question, give feedback, or suggest a new feature. Alternatively, join [bUnits Gitter channel](https://gitter.im/egil/bunit) and let us know. There are no stupid questions - all are welcome!

docs/site/docs/getting-started/writing-tests.md

@@ -230,7 +230,7 @@ Then methods like <xref:Bunit.TestContext.RenderComponent``1(System.Action{Bunit
 > For example, `var cut = ctx.RenderComponent<HelloWorld>();`  
 > becomes `var cut = RenderComponent<HelloWorld>();`.
 
-## Further Reading
+## Further reading
 
 With the basics out of the way, next we will look at how to pass parameters and inject services into our component under test. After that, we will cover ways we can verify the outcome of a rendering in more detail
 

docs/site/docs/interaction/awaiting-async-state.md

@@ -1,9 +1,9 @@
 ---
 uid: awaiting-async-state
-title: Awaiting an Asynchronous State Change in a Component Under Test
+title: Awaiting an asynchronous state change in a component under test
 ---
 
-# Awaiting an Asynchronous State Change
+# Awaiting an asynchronous state change
 
 A test can fail if a component performs asynchronous renders. This may be due to a reason such as waiting for an asynchronous operation to complete before continuing its render life-cycle. For example, if a component is waiting for an async web service to return data to it in the `OnInitializedAsync()` life-cycle method before rendering it to the render tree.
 
@@ -13,7 +13,7 @@ bUnit comes with two methods that help to deal with this issue: the [`WaitForSta
 
 Let's start by taking a look at the `WaitForState` method in more detail.
 
-## Waiting for State Using `WaitForState`
+## Waiting for state using `WaitForState`
 
 The [`WaitForState(Func<Boolean>, TimeSpan?)`](xref:Bunit.RenderedFragmentWaitForHelperExtensions.WaitForState(Bunit.IRenderedFragmentBase,System.Func{System.Boolean},System.Nullable{System.TimeSpan})) method can be used to block and wait in a test method, until the provided predicate returns true or the timeout is reached. (The default timeout is one second.)
 
@@ -38,7 +38,7 @@ This is what happens in the test:
 > [!WARNING]
 > The wait predicate and an assertion should not verify the same thing. Instead, use the `WaitForAssertion(...)` method covered on the <xref:async-assertion> page instead.
  
-### Controlling Wait Timeout
+### Controlling wait timeout
 
 The timeout, which defaults to one second, can be controlled by passing a `TimeSpan` as the second argument to the `WaitForState()` method, e.g.:
 

docs/site/docs/interaction/index.md

@@ -1,9 +1,9 @@
 ---
 uid: interaction
-title: Interacting with a Component Under Test
+title: Interacting with a component under test
 ---
 
-# Interacting with a Component Under Test
+# Interacting with a component under test
 
 This section covers the various ways to interact with a component under test, e.g. trigger event handlers. This — and more — is covered in the following sub sections:
 

docs/site/docs/interaction/trigger-event-handlers.md

@@ -1,9 +1,9 @@
 ---
 uid: trigger-event-handlers
-title: Triggering Event Handlers in Components
+title: Triggering event handlers in components
 ---
 
-# Triggering Event Handlers in Components
+# Triggering event handlers in components
 
 Blazor makes it possible to bind many event handlers to elements in a Blazor component using the `@onXXXX` syntax, e.g. `@onclick="MyClickHandler"`. 
 
@@ -27,7 +27,7 @@ To use these, first find the element in the component under test where the event
 
 The following section demonstrates how to do this...
 
-## Invoking an Event Handler on an Element
+## Invoking an event handler on an element
 
 To invoke an event handler on an element, first find the element in the component under test, and then call the desired event dispatch helper method.
 
@@ -39,11 +39,11 @@ To trigger the `@onclick` `ClickHandler` event handler method in the `<ClickMe>`
 
 # [C# test code](#tab/csharp)
 
-[!code-csharp[ClickMeTest.cs](../../../samples/tests/xunit/ClickMeTest.cs?range=12-23&highlight=7-9)]
+[!code-csharp[ClickMeTest.cs](../../../samples/tests/xunit/ClickMeTest.cs?range=9-25&highlight=10-13)]
 
 # [Razor test code](#tab/razor)
 
-[!code-cshtml[ClickMeTest.razor](../../../samples/tests/razor/ClickMeTest.razor?highlight=17-19)]
+[!code-cshtml[ClickMeTest.razor](../../../samples/tests/razor/ClickMeTest.razor?highlight=12-14)]
 
 ***