From f0ed26ae2a36f1ddd33683662031927fc2a5ff31 Mon Sep 17 00:00:00 2001 From: Martin Date: Tue, 29 Nov 2022 16:34:45 +0100 Subject: [PATCH] Fix minor typo In the deprecation document there is a typo `on` --> `one` Missed that one while reviewing. --- docs/ocis/development/deprecating-variables.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ocis/development/deprecating-variables.md b/docs/ocis/development/deprecating-variables.md index e61549b5b8..4979f2ebf0 100644 --- a/docs/ocis/development/deprecating-variables.md +++ b/docs/ocis/development/deprecating-variables.md @@ -32,8 +32,8 @@ There are four different annotation variables that need to be filled: | depreactionVersion| The version the variable will be deprecated| semver (e.g. 1.6.2)| | removalVersion| The version the variable will be removed from the codebase| semver (e.g. 1.7.3)| | deprecationInfo| Information why the variable is deprecated, must start with the name of the variable in order to avoid confusion, when there are multiple options in the `env:`-field | string (e.g. NATS_NATS_HOST is confusing) | -| depreactionReplacement | The name of the variable that is going to replace the deprecated on.| string (e.g. NATS_HOST_ADDRESS)| +| depreactionReplacement | The name of the variable that is going to replace the deprecated one.| string (e.g. NATS_HOST_ADDRESS)| ### What happens next? -Once a variable has been finally removed, the annotations must be removed again from the code, since they do not serve any purpose from this point. \ No newline at end of file +Once a variable has been finally removed, the annotations must be removed again from the code, since they do not serve any purpose from this point.