Skip to content

chore: fix user-facing and comment typos (reciever, seperator, occured)#794

Closed
SAY-5 wants to merge 1 commit intohashicorp:mainfrom
SAY-5:chore/fix-typos
Closed

chore: fix user-facing and comment typos (reciever, seperator, occured)#794
SAY-5 wants to merge 1 commit intohashicorp:mainfrom
SAY-5:chore/fix-typos

Conversation

@SAY-5
Copy link
Copy Markdown

@SAY-5 SAY-5 commented Apr 24, 2026

Summary

Seven typos across four files; two surface to users via HCL JSON parser diagnostics:

  • json/parser.go — `Missing attribute seperator comma` (two spots) → `separator`
  • json/public.go — `an error occured while closing/reading it.` → `occurred`

Comment-only fixes:

  • diagnostic.go — `recieve` → `receive`, `reciever` → `receiver`
  • pos.go — `reciever` → `receiver` (×3)
  • hclwrite/node.go — `reciever` → `receiver`

Test plan

  • go build ./...
  • go vet ./...
  • go test ./... -count=1 -timeout 120s — full suite green, including hclwrite/fuzz, integrationtest, json, json/fuzz, specsuite

Seven typos across four files, two of which surface to users via
hcl JSON parser diagnostic messages:

  json/parser.go  'Missing attribute seperator comma' (x2)
                  -> 'Missing attribute separator comma'
  json/public.go  'an error occured while closing/reading it.'
                  -> 'an error occurred while closing/reading it.'

Comment-only fixes (no behaviour change):

  diagnostic.go     recieve -> receive, reciever -> receiver
  pos.go            reciever -> receiver (x3)
  hclwrite/node.go  reciever -> receiver

Build, vet, and full test suite all remain green.

Signed-off-by: SAY-5 <say.apm35@gmail.com>
@SAY-5 SAY-5 requested a review from a team as a code owner April 24, 2026 07:21
@hashicorp-cla-app
Copy link
Copy Markdown

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

Have you signed the CLA already but the status is still pending? Recheck it.

1 similar comment
@hashicorp-cla-app
Copy link
Copy Markdown

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

Have you signed the CLA already but the status is still pending? Recheck it.

@crw
Copy link
Copy Markdown
Contributor

crw commented Apr 27, 2026

Thanks for this submission. We generally do not take typo fix PRs unless changes are already being made to the files in question.

@crw crw closed this Apr 27, 2026
This was referenced Apr 28, 2026
This was referenced Apr 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants