From 71ae7e770a3a3e1cf1ef5b0ddea2049acbd114fa Mon Sep 17 00:00:00 2001 From: Valentin Gagarin Date: Mon, 12 Jun 2023 11:10:04 +0200 Subject: [PATCH] fix wording --- rfcs/0137-nix-language-version.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/0137-nix-language-version.md b/rfcs/0137-nix-language-version.md index 544f923..1115eb6 100644 --- a/rfcs/0137-nix-language-version.md +++ b/rfcs/0137-nix-language-version.md @@ -24,7 +24,7 @@ The stability of Nix language has been praised on multiple occasions, e.g. [Nix Yet, as with any software system, in order to accommodate new insights, we want to allow the Nix language to evolve. This sometimes involves backward-incompatible ("breaking") changes that currently cannot be made without significant downstream disruption. -Therefore we propose a mechanims and policies to introduce changes to the Nix language in a controlled and deliberate manner. +Therefore we propose mechanisms and policies for introducing changes to the Nix language in a controlled and deliberate manner. It aims to avoid breaking existing code, to prevent inadvertently breaking reproducibility, and to minimise maintenance burden for implementors and users. ## Motivating examples