From 46b3bf6b5aee1f24898f0a611989f82624c60d92 Mon Sep 17 00:00:00 2001
From: Peter Roche <46547072+paroche@users.noreply.github.com>
Date: Mon, 30 Mar 2020 18:17:55 -0600
Subject: [PATCH] Change 'brackets' to 'parentheses'

I think this is the way it is typically used here and elsewhere. reserving "brackets" without a qualifier for indicating square brackets., so probably no explanation is necessary.

But, for those who want to know more:

It does seem to be the case that in British English "brackets" typically means "round brackets", which are parentheses, but in American English "brackets" typically means square brackets ("[]").

Admittedly, "brackets" is easier to spell. And to pronounce. Even to type, once you get used to it.
---
 .../04-object-methods/2-check-syntax/solution.md                | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/1-js/04-object-basics/04-object-methods/2-check-syntax/solution.md b/1-js/04-object-basics/04-object-methods/2-check-syntax/solution.md
index 0534202a..ba5d3bf0 100644
--- a/1-js/04-object-basics/04-object-methods/2-check-syntax/solution.md
+++ b/1-js/04-object-basics/04-object-methods/2-check-syntax/solution.md
@@ -34,4 +34,4 @@ let user = {
 (user.go)() // John
 ```
 
-Please note that brackets around `(user.go)` do nothing here. Usually they setup the order of operations, but here the dot `.` works first anyway, so there's no effect. Only the semicolon thing matters.
+Please note that parentheses around `(user.go)` do nothing here. Usually they setup the order of operations, but here the dot `.` works first anyway, so there's no effect. Only the semicolon thing matters.