Merge pull request #30431 from rolfedh/Issue#29906

Issue #29906 in file architecture/architecture.adoc

Author: codyhoag

modules/architecture-container-application-benefits.adoc

@@ -5,50 +5,22 @@
 [id="architecture-container-application-benefits_{context}"]
 = The benefits of containerized applications
 
-Using containerized applications offers many advantages over using traditional
-deployment methods. Where applications were once expected to be installed on
-operating systems that included all their dependencies, containers let an
-application carry their dependencies with them. Creating containerized
-applications offers many benefits.
+Using containerized applications offers many advantages over using traditional deployment methods. Where applications were once expected to be installed on operating systems that included all their dependencies, containers let an application carry their dependencies with them. Creating containerized applications offers many benefits.
 
 [id="operating-system-benefits_{context}"]
 == Operating system benefits
 
-Containers use small, dedicated Linux operating systems without a kernel.
-Their file system, networking, cgroups, process tables, and namespaces are
-separate from the host Linux system, but the containers can integrate with the
-hosts seamlessly when necessary. Being based on Linux allows containers to use
-all the advantages that come with the open source development model of rapid
-innovation.
+Containers use small, dedicated Linux operating systems without a kernel. Their file system, networking, cgroups, process tables, and namespaces are separate from the host Linux system, but the containers can integrate with the hosts seamlessly when necessary. Being based on Linux allows containers to use all the advantages that come with the open source development model of rapid innovation.
 
-Because each container uses a dedicated operating system, you can deploy
-applications that require conflicting software dependencies on the same host.
-Each container carries its own dependent software and manages its own
-interfaces, such as networking and file systems, so applications never need to
-compete for those assets.
+Because each container uses a dedicated operating system, you can deploy applications that require conflicting software dependencies on the same host. Each container carries its own dependent software and manages its own interfaces, such as networking and file systems, so applications never need to compete for those assets.
 
 [id="deployment-scaling-benefits_{context}"]
 == Deployment and scaling benefits
 
-If you employ rolling upgrades between major releases of your application, you
-can continuously improve your applications without downtime and still maintain
-compatibility with the current release.
-
-You can also deploy and test a new version of an application alongside the
-existing version. Deploy the new application version in addition to the current
-version. If the container passes your tests, simply deploy more new containers
-and remove the old ones. 
-
-Since all the software dependencies for an application are resolved within the
-container itself, you can use a standardized operating system on each host in your
-data center. You do not need to configure a specific operating system for each
-application host. When your data center needs more capacity, you can deploy
-another generic host system.
-
-Similarly, scaling containerized applications is simple. {product-title} offers
-a simple, standard way of scaling any containerized service. For example, if you
-build applications as a set of microservices rather than large, monolithic
-applications, you can scale the individual microservices individually to meet
-demand. This capability allows you to scale only the required services instead
-of the entire application, which can allow you to meet application demands
-while using minimal resources.
+If you employ rolling upgrades between major releases of your application, you can continuously improve your applications without downtime and still maintain compatibility with the current release.
+
+You can also deploy and test a new version of an application alongside the existing version. If the container passes your tests, simply deploy more new containers and remove the old ones. 
+
+Since all the software dependencies for an application are resolved within the container itself, you can use a standardized operating system on each host in your data center. You do not need to configure a specific operating system for each application host. When your data center needs more capacity, you can deploy another generic host system.
+
+Similarly, scaling containerized applications is simple. {product-title} offers a simple, standard way of scaling any containerized service. For example, if you build applications as a set of microservices rather than large, monolithic applications, you can scale the individual microservices individually to meet demand. This capability allows you to scale only the required services instead of the entire application, which can allow you to meet application demands while using minimal resources.