Skip to content

Commit

Permalink
chore: fix some typos
Browse files Browse the repository at this point in the history
Signed-off-by: oftenoccur <ezc5@sina.com>
  • Loading branch information
oftenoccur committed Apr 11, 2024
1 parent 6461e84 commit 368da81
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion d2cli/main.go
Original file line number Diff line number Diff line change
Expand Up @@ -459,7 +459,7 @@ func compile(ctx context.Context, ms *xmain.State, plugins []d2plugin.Plugin, fs
if os.Getenv("D2_LSP_MODE") == "1" {
// only the parse result is needed if running d2 for lsp,
// if this, "fails", the AST is still valid and can be sent
// to vscode extention
// to vscode extension
ast, err := d2lib.Parse(ctx, string(input), opts)

type LspOutputData struct {
Expand Down
2 changes: 1 addition & 1 deletion docs/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -100,7 +100,7 @@ running:
./ci/e2ereport.sh -delta
```

This gives me a nice HMTL output of what the test expected vs what it got (this was a PR
This gives me a nice HTML output of what the test expected vs what it got (this was a PR
fixing multi-byte character labels):

![screencapture-file-Users-alexanderwang-dev-alixander-d2-e2etests-out-e2e-report-html-2023-02-14-10_15_07](https://user-images.githubusercontent.com/3120367/218822836-bcc517f2-ae3e-4e0d-83f6-2cbaa2fd9275.png)
Expand Down
2 changes: 1 addition & 1 deletion lib/urlenc/urlenc_test.go
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ I just forgot my whole philosophy of life!!!: {
}

// TestChanges makes it explicit in PRs when encoding changes
// Something we might want to know for playground compatability
// Something we might want to know for playground compatibility
func TestChanges(t *testing.T) {
// Choose something with many keywords and varied text
const script = `timeline mixer: "" {
Expand Down

0 comments on commit 368da81

Please sign in to comment.