From 15704737e081488964fbb4604f499dbbb52f949a Mon Sep 17 00:00:00 2001
From: fiftydinar <65243233+fiftydinar@users.noreply.github.com>
Date: Tue, 1 Oct 2024 14:45:14 +0200
Subject: [PATCH] docs: Some more refinements to `readonly`

---
 README.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 049f8c5..31a3d5d 100644
--- a/README.md
+++ b/README.md
@@ -19,10 +19,9 @@ These are general guidelines for writing official bash modules and their documen
 - Echo what you're doing on each step and on errors to help debugging.
 - Implement error-checks for scenarios where the image-maintainer might misconfigure the module.
 - Use `snake_case` for functions and variables changed by the code.  
-  You can utilize `readonly (-f) snake_case` to mark variable or function as read-only when it won't be changed anymore for safety.
 - Use `readonly SCREAMING_SNAKE_CASE` for variables that are set once and stay unchanged.
 - For functions that are set once and stay unchanged, make a function & in next line set:  
-  `readonly -f FUNCTION_NAME`.
+  `readonly -f function_name`.
 - Use `"${variable_name}"` when you want to expose information from the variable & to ensure that variables are properly parsed as strings.
 - If you want to insert another regular string as a suffix or prefix to the `"${variable_name}"`, you should do that in this format: `"prefix-${variable_name}-suffix"`
 - Use `set -euo pipefail` at the start of the script, to ensure that module will fail the image build if error is caught.