fix: docs references

Author: egil

.github/workflows/actions/docfx/Dockerfile

@@ -81,9 +81,9 @@ jobs:
         run: dotnet test docs/samples/samples.sln
 
       - name: 🛠️ Building docs
-        uses: ./workflows/actions/docfx
-        with:
-          args: docs/site/docfx.json
+        run: |
+          dotnet tool update -g docfx --version 2.67.0
+          docfx docs/site/docfx.json
 
       - name: 🛠️ Deploy to GitHub Pages
         if: success()

.github/workflows/actions/docfx/action.yml

@@ -7,7 +7,7 @@ title: Triggering a render life cycle on a component
 
 To trigger a re-render of a component under test, a reference to it through a <xref:Bunit.IRenderedComponent`1> type is needed. When using the <xref:Bunit.TestContext>'s `RenderComponent<TComponent>()` method, this is the type returned.
 
-In `.razor` based tests, using the <xref:Bunit.TestContext>'s <xref:Bunit.TestContext.Render``1(RenderFragment)> method also returns an <xref:Bunit.IRenderedComponent`1> (as opposed to the <xref:Bunit.TestContext.Render(Microsoft.AspNetCore.Components.RenderFragment)> method which returns the more simple <xref:Bunit.IRenderedFragment>).
+In `.razor` based tests, using the <xref:Bunit.TestContext>'s <xref:Bunit.TestContext.Render(Microsoft.AspNetCore.Components.RenderFragment)> method also returns an <xref:Bunit.IRenderedComponent`1> (as opposed to the <xref:Bunit.TestContext.Render(Microsoft.AspNetCore.Components.RenderFragment)> method which returns the more simple <xref:Bunit.IRenderedFragment>).
 
 If you have a <xref:Bunit.IRenderedFragment> or a <xref:Bunit.IRenderedComponent`1> in a test, but need a child component's <xref:Bunit.IRenderedComponent`1>, then use the `FindComponent<TComponent>()` or the `FindComponents<TComponent>()` methods, which traverse down the render tree and finds rendered components.
 

.github/workflows/docs-deploy.yml

@@ -9,7 +9,7 @@ Components are, by default in bUnit, instantiated in the exact same way the regu
 
 It is however possible to control how Blazor components build using .NET 5 or newer are instantiated by bUnit. This enables the possibility to replace one component during testing with another, e.g., to replace a 3rd party component during testing with a "[stub component](https://en.wikipedia.org/wiki/Test_stub)", to make the test easier to write and maintain.
 
-The following sections will describe how to use component factories to control instantiation of components during testing.
+The following sections will describe how to use component factories to control the instantiation of components during testing.
 
 ## Using component factories to control instantiation
 

docs/site/docs/interaction/trigger-renders.md

@@ -70,15 +70,15 @@ Assert.Equal("http://localhost/foo", navMan.Uri);
 
 If a component issues multiple `NavigateTo` calls, then it is possible to inspect the navigation history by accessing the <xref:Bunit.TestDoubles.FakeNavigationManager.History> property. It's a stack based structure, meaning the latest navigations will be first in the collection at index 0.
 
-## Asserting that a navigation was prevented with the `NavigationLock` component
+## Asserting that navigation was prevented with the `NavigationLock` component
 
-The `NavigationLock` component, which was introduced with .NET 7, gives the possibility to intercept the navigation and can even prevent it. bUnit will always create a history entry for prevented or even failed interceptions. This gets reflected in the <xref:Bunit.TestDoubles.NavigationHistory.NavigationState> property, as well as in case of an exception on the <xref:Bunit.TestDoubles.NavigationHistory.Exception> property.
+The `NavigationLock` component, which was introduced with .NET 7, gives the possibility to intercept the navigation and can even prevent it. bUnit will always create a history entry for prevented or even failed interceptions. This gets reflected in the <xref:Bunit.TestDoubles.NavigationHistory> property.
 
 A component can look like this:
 ```razor
 @inject NavigationManager NavigationManager
 
-<button @onclick="(() => NavigationManager.NavigateTo("/counter"))">Counter</button> 
+<button @onclick="(() => NavigationManager.NavigateTo("/counter"))">Counter</button>
 
 <NavigationLock OnBeforeInternalNavigation="InterceptNavigation"></NavigationLock>
 

docs/site/docs/providing-input/controlling-component-instantiation.md

@@ -12,13 +12,13 @@ The test implementation of Blazor's authentication and authorization can be put
 - **Authenticating**
 - **Unauthenticated** and **unauthorized**
 - **Authenticated** and **unauthorized**
-- **Authenticated** and **authorized** 
+- **Authenticated** and **authorized**
 - **Authenticated** and **authorized** with one or more **roles**, **claims**, and/or **policies**
 
 bUnit's authentication and authorization implementation is easily available by calling [`AddTestAuthorization()`](xref:Bunit.TestDoubles.FakeAuthorizationExtensions.AddTestAuthorization(Bunit.TestContextBase)) on a test context. This adds the necessary services to the `Services` collection and the `CascadingAuthenticationState` component to the [root render tree](xref:root-render-tree). The method returns an instance of the <xref:Bunit.TestDoubles.TestAuthorizationContext> type that allows you to control the authentication and authorization state for a test.
 
 > [!NOTE]
-> If your test class inherits directly from bUnit's <xref:Bunit.TestContext>, as described in <xref:writing-tests#remove-boilerplate-code-from-tests>, then you need to call the [`AddTestAuthorization()`](xref:Bunit.TestDoubles.FakeAuthorizationExtensions.AddTestAuthorization(Bunit.TestContextBase)) method on `this`, since `AddTestAuthorization()` is an extension method, otherwise it wont be available. E.g.: `this.AddTestAuthorization()`.
+> If your test class inherits directly from bUnit's <xref:Bunit.TestContext> then you need to call the [`AddTestAuthorization()`](xref:Bunit.TestDoubles.FakeAuthorizationExtensions.AddTestAuthorization(Bunit.TestContextBase)) method on `this`, since `AddTestAuthorization()` is an extension method, otherwise it wont be available. E.g.: `this.AddTestAuthorization()`.
 
 The following sections show how to set each of these states in a test.
 
@@ -62,7 +62,7 @@ To set the state to authenticated and authorized, do the following:
 
 [!code-csharp[UserInfoTest.cs](../../../samples/tests/xunit/UserInfoTest.cs?start=55&end=64&highlight=3)]
 
-After calling `AddTestAuthorization()`, the returned <xref:Bunit.TestDoubles.TestAuthorizationContext> is used to set the authenticated and authorized state through the <xref:Bunit.TestDoubles.TestAuthorizationContext.SetAuthorized(System.String,Bunit.TestDoubles.AuthorizationState)> method. 
+After calling `AddTestAuthorization()`, the returned <xref:Bunit.TestDoubles.TestAuthorizationContext> is used to set the authenticated and authorized state through the <xref:Bunit.TestDoubles.TestAuthorizationContext.SetAuthorized(System.String,Bunit.TestDoubles.AuthorizationState)> method.
 
 Note that the second parameter, `AuthorizationState`, is optional, and defaults to `AuthorizationState.Authorized` if not specified.
 

docs/site/docs/test-doubles/fake-navigation-manager.md

@@ -7,7 +7,7 @@ title: Uploading files to the InputFile component
 
 bUnit comes with integrated support for the [`InputFile`](https://docs.microsoft.com/en-us/aspnet/core/blazor/file-uploads?view=aspnetcore-6.0&pivots=server) component and makes it easy to simulate uploading files.
 
-To upload a file, first find the `InputFile` component in the component under test. Afterwards call the method `UploadFile`:
+To upload a file, first find the `InputFile` component in the component under test. Afterward, call the method `UploadFile`:
 
 ```csharp
 // Create an InputFileContent with string content
@@ -25,5 +25,4 @@ inputFile.UploadFile(fileToUpload);
 // Assertions...
 ```
 
-To upload binary content, create an `InputFileContent`  with the `InputFileContent.CreateFromBinary()` method.
-See all supported properties supported by the `InputFileContent` on its [reference page](xref:Bunit.InputFileContent).
+To upload binary content, create an `InputFileContent` with the `InputFileContent.CreateFromBinary()` method.