@benoittgt very kindly submitted a PR to fix some spacing issues in the markdown using gofmtmd.

It should be possible to automate this as part of the build script

Is your feature request related to a problem? Please describe.
Reading through what a fake can and can not do is not clear from the documentation.

Describe the solution you'd like
Exact methods that are available to a Fake need to be documented.

First of all thank you for Sinon, I believe the library is powerful and has helped me write a lot of tests. What I'm requesting here is

When running build.ps1 -t Test, the following output describes the failing tests:

1. Failed : NUnit.Framework.Api.FrameworkControllerTests.ExploreTestsAction_FileNotFound_ReturnsNonRunnableSuite
   Expected: String containing "The system cannot find the file specified."
   But was: "Le fichier sp├®cifi├® est introuvable. (Exception from HRESULT: 0x80070002)"
   at NUnit.Framework.Api.Framew

Summary

The documentation "activate_announcer_on_command_failure" is not helpful for users as it misses information a

Hello, and thank for this module.
I am wondering if consideration has been given to adding colour to the stack traces printed out upon failure of a test. For a test runner emphasizing colour, this seems like an obvious omission. I have patched in this functionality using pygments in my fork: psacawa/green@1922bc8 in an ad hoc fashion t