Fixing api ref

Author: egil

.github/workflows/CI-CD-Docs.yml

@@ -41,8 +41,7 @@ jobs:
           dotnet build src/bunit.core/ --no-restore -p:version=$VERSION
           dotnet build src/bunit.web/ --no-restore -p:version=$VERSION
           dotnet build src/bunit.xunit/ --no-restore -p:version=$VERSION
-          dotnet build docs/docs.csproj
-          dotnet build docs/docs.csproj
+          dotnet build docs/
       - name: Deploy
         uses: JamesIves/github-pages-deploy-action@releases/v3
         with:

docs/docs.csproj

@@ -10,8 +10,8 @@
     <PackageReference Include="Microsoft.AspNetCore.Components.Web" Version="3.1.4" />
     <PackageReference Include="xunit" Version="2.4.1" />
     <PackageReference Include="nunit" Version="3.12.0" />
-    <PackageReference Include="MSTest.TestFramework" Version="2.1.0" />
-    <PackageReference Include="docfx.console" Version="2.50.0">
+    <PackageReference Include="MSTest.TestFramework" Version="2.1.1" />
+    <PackageReference Include="docfx.console" Version="2.53.1">
       <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
       <PrivateAssets>all</PrivateAssets>
     </PackageReference>

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

@@ -42,7 +42,7 @@ In this test, we do the following:
 
 1. New up the disposable <xref:Bunit.TestContext>, and assign it using the `using var` syntax, to avoid unnecessary indention.
 2. Render the `<HelloWorld>` component using <xref:Bunit.TestContext>, which we do through the <xref:Bunit.TestContext.RenderComponent``1(Bunit.Rendering.ComponentParameter[])> method. We will cover passing parameters to components elsewhere.
-3. Verify the rendered markup from the `<HelloWorld>` component using the <xref:Bunit.MarkupMatchesAssertExtensions.MarkupMatches> method, which performs a semantic comparison of the expected markup with the rendered markup.
+3. Verify the rendered markup from the `<HelloWorld>` component using the `MarkupMatches` method, which performs a semantic comparison of the expected markup with the rendered markup.
 
 > [!TIP]
 > Learn more about how the semantic HTML/markup comparison in bUnit work, and how to customize it on the <xref:semantic-html-comparison> page.

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

@@ -51,7 +51,7 @@ Let's break down what is going on in this test:
 - The <xref:Bunit.Fixture> component's `Test` parameter takes a method, which is called when the test runs, and is passed the <xref:Bunit.Fixture> component.
 - In the test method, we:
   - Use the <xref:Bunit.Fixture.GetComponentUnderTest``1> to get the `HelloWorld` declared in the <xref:Bunit.Fixture>.
-  - Verify the rendered markup from the `HelloWorld` component using the <xref:Bunit.MarkupMatchesAssertExtensions.MarkupMatches> method, which performs a semantic comparison of the expected markup with the rendered markup.
+  - Verify the rendered markup from the `HelloWorld` component using the `MarkupMatches` method, which performs a semantic comparison of the expected markup with the rendered markup.
 
 > [!TIP]
 > Learn more about how the semantic HTML/markup comparison in bUnit work, and how to customize it on the <xref:semantic-html-comparison> page.