SRVCOM-1728: Updating autoscaling docs abstracts for Jupiter

Author: abrennan89

modules/serverless-concurrency-limits.adoc renamed to modules/serverless-about-concurrency.adoc

@@ -1,12 +1,12 @@
 // Module included in the following assemblies:
 //
-// * serverless/develop/serverless-autoscaling-developer.adoc
+// * /serverless/develop/serverless-autoscaling-developer.adoc
 
 :_content-type: CONCEPT
-[id="serverless-concurrency-limits_{context}"]
-= Concurrency limits and targets
+[id="serverless-about-concurrency_{context}"]
+= Concurrency
 
-Concurrency can be configured as either a _soft limit_ or a _hard limit_:
+Concurrency determines the number of simultaneous requests that can be processed by each replica of an application at any given time. Concurrency can be configured as a _soft limit_ or a _hard limit_:
 
 * A soft limit is a targeted requests limit, rather than a strictly enforced bound. For example, if there is a sudden burst of traffic, the soft limit target can be exceeded.
 

modules/serverless-autoscaling-developer-minscale.adoc

@@ -6,16 +6,14 @@
 [id="serverless-autoscaling-developer-minscale_{context}"]
 = Minimum scale bounds
 
-The minimum number of replicas that can serve an application is determined by the `minScale` annotation.
+The minimum number of replicas that can serve an application is determined by the `minScale` annotation. If scale to zero is not enabled, the `minScale` value defaults to `1`.
 
 The `minScale` value defaults to `0` replicas if the following conditions are met:
 
 * The `minScale` annotation is not set
 * Scaling to zero is enabled
 * The class `KPA` is used
 
-If scale to zero is not enabled, the `minScale` value defaults to `1`.
-
 .Example service spec with `minScale` annotation
 [source,yaml]
 ----

modules/serverless-autoscaling-maxscale-kn.adoc

@@ -6,7 +6,7 @@
 [id="serverless-autoscaling-maxscale-kn_{context}"]
 = Setting the maxScale annotation by using the Knative CLI
 
-You can use the `kn service` command with the `--max-scale` flag to create or modify the `--max-scale` value for a service.
+Using the `kn` CLI to set the `maxScale` annotation provides a more streamlined and intuitive user interface over modifying YAML files directly. You can use the `kn service` command with the `--max-scale` flag to create or modify the `--max-scale` value for a service.
 
 .Prerequisites
 

modules/serverless-autoscaling-minscale-kn.adoc

@@ -3,10 +3,10 @@
 // * serverless/develop/serverless-autoscaling-developer.adoc
 
 :_content-type: PROCEDURE
-[id="serverless-autoscaling-minscale_{context}"]
+[id="serverless-autoscaling-minscale-kn_{context}"]
 = Setting the minScale annotation by using the Knative CLI
 
-You can use the `kn service` command with the `--min-scale` flag to create or modify the `--min-scale` value for a service.
+Using the `kn` CLI to set the `minScale` annotation provides a more streamlined and intuitive user interface over modifying YAML files directly. You can use the `kn service` command with the `--min-scale` flag to create or modify the `--min-scale` value for a service.
 
 .Prerequisites
 

modules/serverless-concurrency-limits-configure-hard.adoc

@@ -6,10 +6,7 @@
 [id="serverless-concurrency-limits-configure-hard_{context}"]
 = Configuring a hard concurrency limit
 
-You can specify a hard concurrency limit for your Knative service by modifying the `containerConcurrency` spec or by using the `kn service` command with the correct flags.
-
-// However, a default value can be set for the Revision's containerConcurrency field in config-defaults.yaml.
-// add note about this for admins to see? Need more details about config-defaults though
+A hard concurrency limit is a strictly enforced upper bound requests limit. If concurrency reaches the hard limit, surplus requests are buffered and must wait until there is enough free capacity to execute the requests. You can specify a hard concurrency limit for your Knative service by modifying the `containerConcurrency` spec, or by using the `kn service` command with the correct flags.
 
 .Procedure
 

modules/serverless-concurrency-limits-configure-soft.adoc

@@ -6,7 +6,7 @@
 [id="serverless-concurrency-limits-configure-soft_{context}"]
 = Configuring a soft concurrency target
 
-You can specify a soft concurrency target for your Knative service by setting the `autoscaling.knative.dev/target` annotation in the spec, or by using the `kn service` command with the correct flags.
+A soft limit is a targeted requests limit, rather than a strictly enforced bound. For example, if there is a sudden burst of traffic, the soft limit target can be exceeded. You can specify a soft concurrency target for your Knative service by setting the `autoscaling.knative.dev/target` annotation in the spec, or by using the `kn service` command with the correct flags.
 
 .Procedure
 

serverless/develop/serverless-autoscaling-developer.adoc

@@ -26,9 +26,7 @@ Any limits or targets that you set for a service are measured against a single i
 [id="serverless-autoscaling-developer-scale-bounds"]
 == Scale bounds
 
-Scale bounds determine the minimum and maximum numbers of replicas that can serve an application at any given time.
-
-You can set scale bounds for an application to help prevent cold starts or control computing costs.
+Scale bounds determine the minimum and maximum numbers of replicas that can serve an application at any given time. You can set scale bounds for an application to help prevent cold starts or control computing costs.
 
 // minscale docs
 include::modules/serverless-autoscaling-developer-minscale.adoc[leveloffset=+2]
@@ -38,12 +36,8 @@ include::modules/serverless-autoscaling-minscale-kn.adoc[leveloffset=+3]
 include::modules/serverless-autoscaling-developer-maxscale.adoc[leveloffset=+2]
 include::modules/serverless-autoscaling-maxscale-kn.adoc[leveloffset=+3]
 
-[id="serverless-autoscaling-developer-concurrency"]
-== Concurrency
-
-Concurrency determines the number of simultaneous requests that can be processed by each replica of an application at any given time.
-
-include::modules/serverless-concurrency-limits.adoc[leveloffset=+2]
+// concurrency
+include::modules/serverless-about-concurrency.adoc[leveloffset=+1]
 include::modules/serverless-concurrency-limits-configure-soft.adoc[leveloffset=+2]
 include::modules/serverless-concurrency-limits-configure-hard.adoc[leveloffset=+2]
 include::modules/serverless-target-utilization.adoc[leveloffset=+2]