From cd85c099081cd9a0f0278488fedbb89d6ba438ff Mon Sep 17 00:00:00 2001 From: Max Rabin Date: Mon, 15 Apr 2024 14:54:50 +0300 Subject: [PATCH] Update security-parameters.mdx --- .../running-opal/run-opal-server/security-parameters.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/docs/getting-started/running-opal/run-opal-server/security-parameters.mdx b/documentation/docs/getting-started/running-opal/run-opal-server/security-parameters.mdx index a6d6dfd32..1862e7afd 100644 --- a/documentation/docs/getting-started/running-opal/run-opal-server/security-parameters.mdx +++ b/documentation/docs/getting-started/running-opal/run-opal-server/security-parameters.mdx @@ -6,7 +6,7 @@ In this step we show how to configure the OPAL server **security parameters**. Declaring these parameters and passing them to OPAL server will cause the server to run in **secure mode**, which means client identity verification will be active. All the values in this section are sensitive, in production you should place them in a [secrets store](#security-considerations). -#### When should i run in secure mode? +#### When should I run in secure mode? In a dev environment, secure mode is optional and you can skip this section.