minor doc fix and remove unused constant

Author: alai8

docs-source/content/userguide/managing-domains/configoverrides/_index.md

@@ -340,7 +340,7 @@ Incorrectly formatted override files may be accepted without warnings or errors
 
 On WebLogic Servers that support the `weblogic.SituationalConfig.failBootOnError` system property ( Note: It is not supported in WebLogic Server 12.2.1.3.0 ),
 by default the WebLogic server will fail to boot if any situational configuration files are invalid,
-if it encounters an error while loading situational configuration files.
+or if it encounters an error while loading situational configuration files.
 By setting the `FAIL_BOOT_ON_SITUATIONAL_CONFIG_ERROR` environment variable in the Kubernetes containers for the WebLogic Servers to `false`, you can start up the WebLogic Servers even with incorrectly formatted override files.
 
 * Make sure you've followed each step in the [Step-by-step guide](#step-by-step-guide).

model/src/main/java/oracle/kubernetes/operator/KubernetesConstants.java

@@ -26,7 +26,6 @@ public interface KubernetesConstants {
   String[] DOMAIN_ALTERNATE_VERSIONS = {"v2", "v3"};
 
   boolean DEFAULT_INCLUDE_SERVER_OUT_IN_POD_LOG = true;
-  boolean DEFAULT_FAIL_BOOT_ON_SITUATIONAL_ERROR = true;
 
   String CONTAINER_NAME = "weblogic-server";