First pass at packaging (#161)

* First pass at packaging

* applied feedback

Signed-off-by: Guillermo González de Agüero <z06.guillermo@gmail.com>

src/main/jbake/content/packaging001.adoc

@@ -39,9 +39,9 @@ specified in the source code.
 .*Figure 5-1 EAR File Structure*
 image:img/jakartaeett_dt_010.png[
 "Diagram of EAR file structure. META-INF and web, application client,
-EJB, and resource adapter modules are under the assembly root."]
+enterprise bean, and resource adapter modules are under the assembly root."]
 
-The two types of deployment descriptors are Jakarta EE and runtime. A Java
+The two types of deployment descriptors are Jakarta EE and runtime. A Jakarta
 EE deployment descriptor is defined by a Jakarta EE specification and can
 be used to configure deployment settings on any Jakarta EE-compliant
 implementation. A runtime deployment descriptor is used to configure
@@ -62,8 +62,8 @@ module.
 
 Jakarta EE modules are of the following types:
 
-* EJB modules, which contain class files for enterprise beans and,
-optionally, an EJB deployment descriptor. EJB modules are packaged as
+* Enterprise bean modules, which contain class files for enterprise beans and,
+optionally, an enterprise bean deployment descriptor. Enterprise bean modules are packaged as
 JAR files with a `.jar` extension.
 * Web modules, which contain servlet class files, web files, supporting
 class files, GIF and HTML files, and, optionally, a web application

src/main/jbake/content/packaging002.adoc

@@ -12,25 +12,25 @@ Packaging Enterprise Beans
 Packaging Enterprise Beans
 --------------------------
 
-This section explains how enterprise beans can be packaged in EJB JAR or
+This section explains how enterprise beans can be packaged in enterprise bean JAR or
 WAR modules. It includes the following sections:
 
-* link:#packaging-enterprise-beans-in-ejb-jar-modules[Packaging Enterprise Beans in EJB JAR Modules]
+* link:#packaging-enterprise-beans-in-ejb-jar-modules[Packaging Enterprise Beans in enterprise bean JAR Modules]
 * link:#packaging-enterprise-beans-in-war-modules[Packaging Enterprise Beans in WAR Modules]
 
 [[CHDFCDBG]][[packaging-enterprise-beans-in-ejb-jar-modules]]
 
-Packaging Enterprise Beans in EJB JAR Modules
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Packaging Enterprise Beans in enterprise bean JAR Modules
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-An EJB JAR file is portable and can be used for various applications.
+An enterprise bean JAR file is portable and can be used for various applications.
 
 To assemble a Jakarta EE application, package one or more modules, such as
-EJB JAR files, into an EAR file, the archive file that holds the
+enterprise bean JAR files, into an EAR file, the archive file that holds the
 application. When deploying the EAR file that contains the enterprise
-bean's EJB JAR file, you also deploy the enterprise bean to GlassFish
-Server. You can also deploy an EJB JAR that is not contained in an EAR
-file. link:#BCGFJIJI[Figure 5-2] shows the contents of an EJB JAR file.
+bean's enterprise bean JAR file, you also deploy the enterprise bean to GlassFish
+Server. You can also deploy an enterprise bean JAR that is not contained in an EAR
+file. link:#BCGFJIJI[Figure 5-2] shows the contents of an enterprise bean JAR file.
 
 [[BCGFJIJI]]
 
@@ -63,8 +63,8 @@ WAR modules that contain enterprise beans do not require an
 directory.
 
 JAR files that contain enterprise bean classes packaged within a WAR
-module are not considered EJB JAR files, even if the bundled JAR file
-conforms to the format of an EJB JAR file. The enterprise beans
+module are not considered enterprise bean JAR files, even if the bundled JAR file
+conforms to the format of an enterprise bean JAR file. The enterprise beans
 contained within the JAR file are semantically equivalent to enterprise
 beans located in the WAR module's `WEB-INF/classes` directory, and the
 environment namespace of all the enterprise beans are scoped to the WAR

src/main/jbake/content/packaging003.adoc

@@ -16,7 +16,7 @@ In the Jakarta EE architecture, a web module is the smallest deployable and
 usable unit of web resources. A web module contains web components and
 static web content files, such as images, which are called web
 resources. A Jakarta EE web module corresponds to a web application as
-defined in the Java Servlet specification.
+defined in the Jakarta Servlet specification.
 
 In addition to web components and web resources, a web module can
 contain other files:
@@ -37,9 +37,9 @@ enterprise bean class files, utility classes, and JavaBeans components
 * `lib`, a directory that contains JAR files that contain enterprise
 beans, and JAR archives of libraries called by server-side classes
 * Deployment descriptors, such as `web.xml` (the web application
-deployment descriptor) and `ejb-jar.xml` (an EJB deployment descriptor)
+deployment descriptor) and `ejb-jar.xml` (an enterprise bean deployment descriptor)
 
-A web module needs a `web.xml` file if it uses JavaServer Faces
+A web module needs a `web.xml` file if it uses Jakarta Server Faces
 technology, if it must specify certain kinds of security information, or
 if you want to override information specified by web component
 annotations.
@@ -52,7 +52,7 @@ A web module can be deployed as an unpacked file structure or can be
 packaged in a JAR file known as a Web Archive (WAR) file. Because the
 contents and use of WAR files differ from those of JAR files, WAR file
 names use a `.war` extension. The web module just described is portable;
-you can deploy it into any web container that conforms to the Java
+you can deploy it into any web container that conforms to the Jakarta
 Servlet specification.
 
 You can provide a runtime deployment descriptor (DD) when you deploy a

src/main/jbake/content/packaging004.adoc

@@ -13,7 +13,7 @@ Packaging Resource Adapter Archives
 -----------------------------------
 
 A Resource Adapter Archive (RAR) file stores XML files, Java classes,
-and other objects for Jakarta EE Connector Architecture (JCA) applications.
+and other objects for Jakarta EE Connector applications.
 A resource adapter can be deployed on any Jakarta EE server, much like a
 Jakarta EE application. A RAR file can be contained in an Enterprise
 Archive (EAR) file, or it can exist as a separate file.