From 300aa418fbd7ff305c0a64f10e45096464b58fa3 Mon Sep 17 00:00:00 2001
From: Brett Meyer <brett@3riverdev.com>
Date: Thu, 20 Aug 2015 12:18:17 -0400
Subject: [PATCH] HHH-10041 doc correction

---
 .../src/main/docbook/userGuide/en-US/chapters/osgi/OSGi.xml     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/src/main/docbook/userGuide/en-US/chapters/osgi/OSGi.xml b/documentation/src/main/docbook/userGuide/en-US/chapters/osgi/OSGi.xml
index b75d716554..db7a2d8138 100644
--- a/documentation/src/main/docbook/userGuide/en-US/chapters/osgi/OSGi.xml
+++ b/documentation/src/main/docbook/userGuide/en-US/chapters/osgi/OSGi.xml
@@ -111,7 +111,7 @@
           <para>
             In order to utilize container-managed JPA, an Enterprise OSGi JPA container must be active in the runtime.
             In Karaf, this means Aries JPA, which is included out-of-the-box (simply activate the <literal>jpa</literal>
-            and <literal>jta</literal> features).  Originally, we intended to include those dependencies within our own
+            and <literal>transaction</literal> features).  Originally, we intended to include those dependencies within our own
             <literal>features.xml</literal>.  However, after guidance from the Karaf and Aries teams, it was pulled out.
             This allows Hibernate OSGi to be portable and not be directly tied to Aries versions, instead having
             the user choose which to use.