From ffbcefb62957f6695d9eab3ea8b804dcce311125 Mon Sep 17 00:00:00 2001 From: epriestley Date: Mon, 28 Sep 2015 04:13:36 -0700 Subject: [PATCH] Fix a doc typo Summary: chack spels Test Plan: typey typey Reviewers: chad, hach-que Reviewed By: hach-que Differential Revision: https://secure.phabricator.com/D14175 --- src/docs/user/field/exit_codes.diviner | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/docs/user/field/exit_codes.diviner b/src/docs/user/field/exit_codes.diviner index a49083b934..7c69b3509b 100644 --- a/src/docs/user/field/exit_codes.diviner +++ b/src/docs/user/field/exit_codes.diviner @@ -151,7 +151,7 @@ command-line tools, and much easier to react to exit codes. This is sometimes used as an argument for communicating application status in exit codes. We reject this because we don't think you should be writing `bash` scripts if -you're doing real operations. Funadmentally, `bash` shell scripts are not a +you're doing real operations. Fundamentally, `bash` shell scripts are not a robust building block for creating correct, reliable operational processes. Here is one problem with using `bash` scripts to perform operational tasks. -- 2.51.2