From d1600211e5e1e6f61085159373432562f53973b9 Mon Sep 17 00:00:00 2001 From: Aaron Gyes Date: Mon, 14 Feb 2022 16:18:16 -0800 Subject: [PATCH] Docs: Posix -> POSIX --- doc_src/design.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc_src/design.rst b/doc_src/design.rst index 8fcc7edb9..885fa3d9e 100644 --- a/doc_src/design.rst +++ b/doc_src/design.rst @@ -9,7 +9,7 @@ This is a description of the design principles that have been used to design fis 2. Fish should be user friendly, but not at the expense of expressiveness. Most tradeoffs between power and ease of use can be avoided with careful design. -3. Whenever possible without breaking the above goals, fish should follow the Posix syntax. +3. Whenever possible without breaking the above goals, fish should follow POSIX. To achieve these high-level goals, the fish design relies on a number of more specific design principles. These are presented below, together with a rationale and a few examples for each.