From fe257d4b90f7ee7e185fade5e605eb9a2a051214 Mon Sep 17 00:00:00 2001 From: Paul Jolly Date: Mon, 3 Jun 2024 14:05:16 +0100 Subject: [PATCH] modules: fix typos MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Spotted by extemporalgenome in #2 and #3 but because of Gerrit being strict that the commit email addressed and "Signed-Of-By" are the same it was quicker/simpler to make the changes again. Signed-off-by: Paul Jolly Change-Id: I6d85fef64939c6f920c48c594a7ec844fe06b5c8 Reviewed-on: https://review.gerrithub.io/c/cue-lang/proposal/+/1195638 Reviewed-by: Daniel Martí TryBot-Result: CUEcueckoo --- designs/2330-modules-v2.md | 4 ++-- designs/modules/2451-modules-compat.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/designs/2330-modules-v2.md b/designs/2330-modules-v2.md index 16a9e0a..734889f 100644 --- a/designs/2330-modules-v2.md +++ b/designs/2330-modules-v2.md @@ -100,7 +100,7 @@ This is proposed [here](./modules/2451-modules-compat.md). ### Compatibility Attributes Sometimes publishers will deliberately break compatibility. -For instane, features may be deprecated or removed, some features +For instance, features may be deprecated or removed, some features may be changed during an alpha or beta release cycle, while feature flags may be valid for a limited time only if they correspond to an experiment. @@ -146,7 +146,7 @@ section we discuss some of the details along with motivations for the design. ### Rationale -Most schema stores and package managers for programming languages follow follow +Most schema stores and package managers for programming languages follow a registry design. For example, Rust with [crates.io](https://crates.io/) and JavaScript with [NPM](https://www.npmjs.com/). diff --git a/designs/modules/2451-modules-compat.md b/designs/modules/2451-modules-compat.md index 36aada8..5d640dd 100644 --- a/designs/modules/2451-modules-compat.md +++ b/designs/modules/2451-modules-compat.md @@ -58,7 +58,7 @@ For this proposal we will focus on backwards compatibility for definitions only. We propose to support a backwards compatibility checks for definitions based on subsumption: -- a major change occurs when a newer defintion does not subsume an older +- a major change occurs when a newer definition does not subsume an older version, - a minor change occurs when a newer definition subsumes an older version, and is not semantically equivalent to this older version, @@ -254,7 +254,7 @@ rules. However, not doing so may result in uncaught bugs and may even pose a security issue. -The CUE tooling should therefore allow for a process by which the compatibility +The CUE tooling should therefore allow for a process by which the compatibility rule can be bypassed. We are aware of this need and are still figuring out how to best go about this.