From c12b125bb15edbe3c0c68c08701d2d177b1f2ec0 Mon Sep 17 00:00:00 2001 From: b murphy Date: Fri, 5 Jan 2024 16:40:11 +0000 Subject: [PATCH] Docs: Update to US English per Writers Toolkit, plus clean up some grammar (#76298) Co-authored-by: Jack Baldry Co-authored-by: tonypowa <45235678+tonypowa@users.noreply.github.com> --- contribute/backend/style-guide.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/contribute/backend/style-guide.md b/contribute/backend/style-guide.md index 17a063d3dc5..39fb84c3cdb 100644 --- a/contribute/backend/style-guide.md +++ b/contribute/backend/style-guide.md @@ -66,8 +66,8 @@ Use [`t.Cleanup`](https://golang.org/pkg/testing/#T.Cleanup) to clean up resourc ### Mock -Optionally, we use [`mock.Mock`](https://github.com/stretchr/testify#mock-package) package to write mocks. This is -useful when you expect different behaviours of the same function. +Optionally, we use [`mock.Mock`](https://github.com/stretchr/testify#mock-package) package to write mocks. +This is useful when you expect different behaviors of the same function. #### Tips @@ -126,7 +126,7 @@ assert.Equal(t, resp.Message, objectToReturn.Message) #### Mockery -When an interface to test is too big, it's annoying to mock each function manually. To avoid this, you can +When an interface to test is too big, it may be toilsome to mock each function manually. To avoid this, you can use [`mockery`](https://github.com/vektra/mockery) library to generate the mocks. The command is like the following (there are more options documented if you need to use another one):