Update

Signed-off-by: A.Arnold <[email protected]>

Author: anarnold97

docs/topics/mta-requirements-for-java-analyzer.adoc

@@ -6,15 +6,13 @@
 [id="mta-requirements-for-java-analyzer_{context}"]
 = Adding minimum requirements for Java analyzer and discovery
 
-There is a minimum required for the Java analyzer, and as a result, the  discovery task.
+There is a minimum requirement for the Java analyzer, and also the discovery task, which by default is set to 2 GiB.
 
-The suggested requirement is a default minimum of 2 GiB. 
+While this minimum requirement can be lowered to  1.5 GiB, it is not recommended.
 
-The minimum requirement can be lowered to  1.5 GiB. However, this minimum requirement is not recommended. 
+You can also increase this minimum requirement to more than 2 GiB.
 
-This minimum requirement can be set in `provider_java_container_limits_memory` and `provider_java_container_requests_memory` options in the Tackle custom resource.
-
-[source,yaml]
+[source, yaml]
 ----
 kind: Tackle
 apiVersion: tackle.konveyor.io/v1alpha1
@@ -26,3 +24,8 @@ spec:
   provider_java_container_limits_memory: 2Gi
   provider_java_container_requests_memory: 2Gi
 ----
+
+[NOTE]
+====
+To guarantee scheduling has the correct space, `provider_java_container_limits_memory` and `provider_java_container_requests_memory` should be assigned the same amount of space.
+====