@dennisdoomen @jnyrup

I've updated the documentation and tested that the site still looks good locally.

In terms of the comment I made above about how I would like to reduce the amount of duplicated code, this actually doesn't seem entirely feasible at this point and appears to be a widespread issue in the solution, including the areas where I deleted old code.
An example is that it seems difficult to share common functionality easily between FunctionAssertions and AsyncFunctionAssertions, (i.e. the ThrowExactly method) as they don't use a common type. Perhaps in a future item we can look at strategies for refactoring this logic so we have to worry less about duplicate implementations of common methods?

In terms of this PR, do you have any other suggestions for other changes to be made at this stage, or are things at least good enough for this fix to be merged?

Thanks very much :)

An example is that it seems difficult to share common functionality easily between FunctionAssertions and AsyncFunctionAssertions, (i.e. the ThrowExactly method) as they don't use a common type. P

Actually, this is exactly what I did in #1048.

Actually, this is exactly what I did in #1048.

Thanks, I'll check out what you did in that PR and try and refactor things in a similar way.

Or rebase on mine ;-)

Or rebase on mine ;-)

I gave rebasing a go and had a look over all the changes but it turns out they weren't really in line with what I needed to reduce the duplicate code between AsyncFunctionAssertions and ActionAssertions.

I took a different approach which you can see here #1054

Awaiting merge of #1054

@dennisdoomen that duplicate code has now been removed, due to merging in the latest refactorings from master.

Please let me know if there's any other changes needed for this PR.

Thanks very much