Fixed typo in introduction page by tealamore · Pull Request #3019 · fluentassertions/fluentassertions · GitHub
Skip to content

Fixed typo in introduction page#3019

Merged
dennisdoomen merged 1 commit into
fluentassertions:mainfrom
tealamore:fix/typoInIntroductionPage
Feb 14, 2025
Merged

Fixed typo in introduction page#3019
dennisdoomen merged 1 commit into
fluentassertions:mainfrom
tealamore:fix/typoInIntroductionPage

Conversation

@tealamore

Copy link
Copy Markdown
Contributor

This fixes an error in the introduction page. Presently it shows the assertion

    5.Should().Be(10);

and says the output would be

Expected value to be 100, but found 95 (difference of -5).

The correct output would be

Expected value to be 10, but found 5 (difference of -5).

IMPORTANT

  • If the PR touches the public API, the changes have been approved in a separate issue with the "api-approved" label.
  • The code complies with the Coding Guidelines for C#.
  • The changes are covered by unit tests which follow the Arrange-Act-Assert syntax and the naming conventions such as is used in these tests.
  • If the PR adds a feature or fixes a bug, please update the release notes with a functional description that explains what the change means to consumers of this library, which are published on the website.
  • If the PR changes the public API the changes needs to be included by running AcceptApiChanges.ps1 or AcceptApiChanges.sh.
  • If the PR affects the documentation, please include your changes in this pull request so the documentation will appear on the website.
    • Please also run ./build.sh --target spellcheck or .\build.ps1 --target spellcheck before pushing and check the good outcome

@github-actions

Copy link
Copy Markdown

@dennisdoomen dennisdoomen merged commit 886ac05 into fluentassertions:main Feb 14, 2025
@dennisdoomen

Copy link
Copy Markdown
Member

This was referenced Jul 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants