From 03f7359a4953f40bd8cb4af2f5764de3d0700a1e Mon Sep 17 00:00:00 2001 From: Zearin Date: Sun, 5 Jan 2025 14:32:56 -0500 Subject: [PATCH] =?UTF-8?q?docs:=20=E2=80=9Ccan=20not=E2=80=9D=20=E2=96=B6?= =?UTF-8?q?=EF=B8=8E=20=E2=80=9Ccannot=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- frontend/docs/about-slow-types.md | 6 +++--- frontend/docs/faq.md | 4 ++-- frontend/docs/packages.md | 4 ++-- frontend/docs/private-registries.md | 4 ++-- frontend/docs/scopes.md | 2 +- 5 files changed, 10 insertions(+), 10 deletions(-) diff --git a/frontend/docs/about-slow-types.md b/frontend/docs/about-slow-types.md index 65605377..f2944b5b 100644 --- a/frontend/docs/about-slow-types.md +++ b/frontend/docs/about-slow-types.md @@ -139,7 +139,7 @@ Constants should have explicit type annotations: ### Global augmentation Module augmentation and global augmentation must not be used. This means that -packages can not use `declare global` to introduce new global variables, or +packages cannot use `declare global` to introduce new global variables, or `declare module` to augment other modules. Here are some examples of unsupported code: @@ -343,7 +343,7 @@ are: ## Ignoring slow types -Due to their nature of affecting _if_ JSR can understand the code, you can not +Due to their nature of affecting _if_ JSR can understand the code, you cannot selectively ignore individual diagnostics for slow types. Slow type diagnostics can only be ignored for the entire package. Doing this results in incomplete documentation and type declarations for the package, and slower type checking @@ -367,7 +367,7 @@ adding the following to your `deno.json` configuration file: } ``` -Note that because slow type diagnostics can not be individually ignored, one can +Note that because slow type diagnostics cannot be individually ignored, one can not use an ignore comment like `// deno-lint-ignore no-slow-types` to ignore slow type diagnostics. diff --git a/frontend/docs/faq.md b/frontend/docs/faq.md index b40b1b66..a19138b5 100644 --- a/frontend/docs/faq.md +++ b/frontend/docs/faq.md @@ -59,7 +59,7 @@ foreseeable future - JSR is designed to be very cheap to run. ## Can I delete a package from JSR? -Source code published to JSR can not be deleted. +Source code published to JSR cannot be deleted. [Learn more about immutability.](/docs/immutability) You can "yank" a version of a package, which will hide the version from the @@ -118,7 +118,7 @@ true.** JSR can act on your behalf only to read any resources you have granted it access to (your email addresses and public profile information). It cannot perform arbitrary actions on your behalf. -JSR can not modify your GitHub account, create repositories, create comments, or +JSR cannot modify your GitHub account, create repositories, create comments, or do anything else that would be considered "acting on your behalf". GitHub presents this "Act on your behalf" screen to all GitHub Apps, regardless of what permissions they actually request. diff --git a/frontend/docs/packages.md b/frontend/docs/packages.md index 1458e7ba..ea90242d 100644 --- a/frontend/docs/packages.md +++ b/frontend/docs/packages.md @@ -86,7 +86,7 @@ A package can be deleted from the "Settings" tab on the package page. Only scope admins can delete a package. Packages can only be deleted if they have no published versions. If a package -has published versions, it can not be deleted. +has published versions, it cannot be deleted. [Learn more about registry immutability.](/docs/immutability) When you have a package that you no longer want to maintain, we recommend @@ -118,7 +118,7 @@ file before running `jsr publish` or `deno publish`. ### Yanking versions -Package versions can not be deleted. However, sometimes you may want to prevent +Package versions cannot be deleted. However, sometimes you may want to prevent users from using a specific version of your package, for example because it contains a critical bug. In this case you can "yank" the version. diff --git a/frontend/docs/private-registries.md b/frontend/docs/private-registries.md index 43c8f446..088a526f 100644 --- a/frontend/docs/private-registries.md +++ b/frontend/docs/private-registries.md @@ -75,7 +75,7 @@ the Azure DevOps Artifacts feed. ### Configuring a JSR upstream with Google Artifact Registry -JSR can not yet be used as an upstream for Google Artifact Registry due to a +JSR cannot yet be used as an upstream for Google Artifact Registry due to a differing layout of package tarball URLs between JSR and the layout that is expected by Google Artifact Registry. @@ -84,7 +84,7 @@ Aligning JSRs package tarball URLs with the NPM upstream is being tracked in ### Configuring a JSR upstream with JFrog Artifactory -JSR can not yet be used as an upstream for JFrog Artifactory due to a differing +JSR cannot yet be used as an upstream for JFrog Artifactory due to a differing layout of package tarball URLs between JSR and the layout that is expected by JFrog Artifactory. diff --git a/frontend/docs/scopes.md b/frontend/docs/scopes.md index fa7db66b..d7d7134a 100644 --- a/frontend/docs/scopes.md +++ b/frontend/docs/scopes.md @@ -60,7 +60,7 @@ can also see all pending invitations on their Admins can change the role of other members. To change the role of a member, head to the "Members" tab of your scope, click the dropdown next to the member you want to change the role of, and select the new role. The new role will take -effect immediately. Note that you can not demote the last admin of a scope to a +effect immediately. Note that you cannot demote the last admin of a scope to a member. If you want to demote the last admin of a scope to a member, you must first promote another member to an admin. A scope must always have at least one admin.