encrypt_secrets no longer available (#1083)

Author: dimisjim

Diff for: README.md

@@ -233,7 +233,7 @@ You are now ready to run action workloads on self hosted runner. Remember that b
 
 ### Encryption
 
-The module support 3 scenario's to manage environment secrets and private key of the Lambda functions.
+The module support 2 scenarios to manage environment secrets and private key of the Lambda functions.
 
 #### Encrypted via a module managed KMS key (default) <!-- omit in toc -->
 
@@ -257,10 +257,6 @@ module "runners" {
 
 ```
 
-#### No encryption <!-- omit in toc -->
-
-Not advised but you can disable the encryption as by setting the variable `encrypt_secrets` to `false`.
-
 ### Idle runners
 
 The module will scale down to zero runners be default, by specifying a `idle_config` config idle runners can be kept active. The scale down lambda checks if any of the cron expressions matches the current time with a marge of 5 seconds. When there is a match the number of runners specified in the idle config will be kept active. In case multiple cron expressions matches only the first one is taken in to account. Below an idle configuration for keeping runners active from 9 to 5 on working days.