Skip to content
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.

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

Fix typo in Future Keywords document #5192

Merged
merged 1 commit into from Sep 30, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/content/policy-language.md
Expand Up @@ -1414,7 +1414,7 @@ To ensure backwards-compatibility, new keywords (like `every`) are introduced sl
In the first stage, users can opt-in to using the new keywords via a special import:

- `import future.keywords` introduces _all_ future keywords, and
- `import future.keyword.x` _only_ introduces the `x` keyword -- see below for all known future keywords.
- `import future.keywords.x` _only_ introduces the `x` keyword -- see below for all known future keywords.

{{< danger >}}
Using `import future.keywords` to import all future keywords means an **opt-out of a
Expand Down