[pmg-devel] [PATCH docs] important service daemons: fix typos and grammar

[Thomas Lamprecht]

On 4/23/20 11:54 AM, Stoiko Ivanov wrote:
>> @@ -75,10 +75,10 @@ You can define the cipher list in `/etc/default/pmgproxy`, for example
>>  
>>   CIPHERS="ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256"
>>  
>> -Above is the default. See the ciphers(1) man page from the openssl
>> +Above is the default. See the `ciphers(1)` man page from the `openssl`
>>  package for a list of all available options.
>>  
>> -Additionally you can define that the client choses the used cipher in
>> +Additionally you can define the order that the client chooses the used cipher in
> you can define that the client chooses in which order the ciphers are used
> (else the server chooses)
> 

All variants where confusing to me, I changed this to:

> The first of these ciphers, available to both the client and the `pmgproxy`,
> will be used.
> 
> Additionally you can allow the client to choose the cipher from the list above
> by disabling the HONOR_CIPHER_ORDER option in `/etc/default/pmgproxy`:
> 
>  HONOR_CIPHER_ORDER=0


Albeit the "HONOR_CIPHER_ORDER" option should be called "FORCE_CIPHER_ORDER"
in the first place.. Anyway, I hope it is somewhat OK now..