File 1024-ssh-Minor-doc-clearification.patch of Package erlang

Overview Repositories Revisions Requests Users Attributes Meta

File 1024-ssh-Minor-doc-clearification.patch of Package erlang

From 0e0bde1f0d9470a118acb04a02e985642067792b Mon Sep 17 00:00:00 2001
From: Hans Nilsson <hans@erlang.org>
Date: Wed, 3 Aug 2022 16:22:20 +0200
Subject: [PATCH] ssh: Minor doc clearification

---
 lib/ssh/doc/src/configurations.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lib/ssh/doc/src/configurations.xml b/lib/ssh/doc/src/configurations.xml
index d4172d0ad8..56dc84e7e0 100644
--- a/lib/ssh/doc/src/configurations.xml
+++ b/lib/ssh/doc/src/configurations.xml
@@ -105,7 +105,7 @@
 There is an ordering, which is:
 
 <list>
- <item>Level 0: Hard-coded default values in the source code</item>
+ <item>Level 0: Hard-coded default values in the OTP SSH source code</item>
 <item>Level 1: <seefile marker="kernel:config">OTP Configuration Parameters</seefile></item>
 <item>Level 2: Options in the <seefile marker="kernel:config">OTP Configuration Parameters</seefile>
 <c>server_options</c> or <c>client_options</c></item>
@@ -116,7 +116,7 @@
 The only exception is the
 <seetype marker="ssh#modify_algorithms_common_option">modify_algorithms</seetype>
 common option. They are all applied in ascending level order on the set of algorithms. So a
- <c>modify_algorithms</c> on level zero is applied before one of level one and so on.
+ <c>modify_algorithms</c> on level one is applied before one of level two and so on.
 
 If there is an
 <seetype marker="ssh#preferred_algorithms_common_option">preferred_algorithms</seetype>
-- 
2.35.3

Places

File 1024-ssh-Minor-doc-clearification.patch of Package erlang

Places