From db12a9c4ae5e09e4899739c5c24e8766e3a9f2b7 Mon Sep 17 00:00:00 2001 From: Aaron Liu Date: Sun, 11 Feb 2024 14:47:32 -0500 Subject: [PATCH] =?UTF-8?q?Docs:=20the=20deleted=20=E2=86=92=20be=20delete?= =?UTF-8?q?d?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/Cask-Cookbook.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Cask-Cookbook.md b/docs/Cask-Cookbook.md index 90f2de1e20..c7447dc36a 100644 --- a/docs/Cask-Cookbook.md +++ b/docs/Cask-Cookbook.md @@ -440,7 +440,7 @@ depends_on arch: :arm64 `desc` accepts a single-line UTF-8 string containing a short description of the software. It’s used to help with searchability and disambiguation, thus it must concisely describe what the software does (or what you can accomplish with it). -`desc` is not for app slogans! Vendors’ descriptions tend to be filled with generic adjectives such as “modern” and “lightweight”. Those are meaningless marketing fluff (do you ever see apps proudly describing themselves as outdated and bulky?) which must the deleted. It’s fine to use the information on the software’s website as a starting point, but it will require editing in almost all cases. +`desc` is not for app slogans! Vendors’ descriptions tend to be filled with generic adjectives such as “modern” and “lightweight”. Those are meaningless marketing fluff (do you ever see apps proudly describing themselves as outdated and bulky?) which must be deleted. It’s fine to use the information on the software’s website as a starting point, but it will require editing in almost all cases. #### Dos and Don'ts