Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
chore(docs): fix code blocks without language settings
  • Loading branch information
Abirdcfly authored and onsi committed Sep 19, 2022
1 parent 07c71e3 commit cf611c4
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/index.md
Expand Up @@ -1131,7 +1131,7 @@ So far we've focused on how Ginkgo specs are constructed using nested nodes and

You typically use a matcher library, like [Gomega](https://github.com/onsi/gomega) to make assertions in your spec. When a Gomega assertion fails, Gomega generates a failure message and passes it to Ginkgo to signal that the spec has failed. It does this via Ginkgo's global `Fail` function. Of course, you're allowed to call this function directly yourself:

```
```go
It("can read books", func() {
if book.Title == "Les Miserables" && user.Age <= 3 {
Fail("User is too young for this book")
Expand Down Expand Up @@ -4109,7 +4109,7 @@ Describe("Repaginating Books", func() {

Now when this spec runs Ginkgo will print out a report detailing the experiment:

```
```bash
Will run 1 of 1 specs
------------------------------
• [2.029 seconds]
Expand Down

0 comments on commit cf611c4

Please sign in to comment.