Skip to content

docs: fix typos and update copyright year in style guide #2968

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thisisjofrank merged 2 commits into from
Mar 12, 2026
Merged

docs: fix typos and update copyright year in style guide #2968

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
47f0bf8
docs: fix typos and update copyright year in style guide
tomas-zijdemans Mar 12, 2026
aaaea78
Merge branch 'main' into grammar-style-guide
thisisjofrank Mar 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions runtime/contributing/style_guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ guide for users of Deno.
Most modules in the repository should have the following copyright header:

```ts
// Copyright 2018-2024 the Deno authors. All rights reserved. MIT license.
// Copyright 2018-2026 the Deno authors. All rights reserved. MIT license.
```

If the code originates elsewhere, ensure that the file has the proper copyright
Expand Down Expand Up @@ -366,7 +366,7 @@ export function foo(): string {
Regular functions and arrow functions have different behavior with respect to
hoisting, binding, arguments, and constructability. The `function` keyword
clearly indicates the intent to define a function, improving legibility and
tracibility while debugging.
traceability while debugging.

#### Error Messages

Expand Down Expand Up @@ -405,7 +405,7 @@ Bad: Cannot parse input hello, world
Good: Cannot parse input "hello, world"
```

4. Message should state the action that lead to the error:
4. Message should state the action that led to the error:

```sh
Bad: Invalid input x
Expand Down
Loading