Fix typos in documentations.
Fix typos in READMEs, javadoc, comments and code. Original pull request #642
This commit is contained in:
committed by
Jens Schauder
parent
1aec184ff0
commit
ce994f9ea0
@@ -38,8 +38,8 @@ import org.springframework.util.Assert;
|
||||
* create a dedicated annotation meta-annotated with {@code @Transactional("…")} to be able to refer to a particular
|
||||
* data source without using String qualifiers.
|
||||
* <p>
|
||||
* Also, not that one cannot interact with both databases in a single, transactional method as transactions are thread
|
||||
* bound in Spring an thus only a single transaction can be active in a single thread. See {@link Application#init()}
|
||||
* Also, note that one cannot interact with both databases in a single, transactional method as transactions are thread
|
||||
* bound in Spring and thus only a single transaction can be active in a single thread. See {@link Application#init()}
|
||||
* for how to orchestrate the calls.
|
||||
*
|
||||
* @author Oliver Gierke
|
||||
|
||||
@@ -32,7 +32,7 @@ import org.springframework.transaction.PlatformTransactionManager;
|
||||
* Configuration for the {@link Customer} slice of the system. A dedicated {@link DataSource},
|
||||
* {@link JpaTransactionManager} and {@link EntityManagerFactory}. Note that there could of course be some deduplication
|
||||
* with {@link example.springdata.jpa.multipleds.order.OrderConfig}. I just decided to keep it to focus on the
|
||||
* sepeartion of the two. Also, some overlaps might not even occur in real world scenarios (whether to create DDl or the
|
||||
* separation of the two. Also, some overlaps might not even occur in real world scenarios (whether to create DDl or the
|
||||
* like).
|
||||
*
|
||||
* @author Oliver Gierke
|
||||
|
||||
@@ -32,7 +32,7 @@ import org.springframework.transaction.PlatformTransactionManager;
|
||||
* Configuration for the {@link Order} slice of the system. A dedicated {@link DataSource},
|
||||
* {@link JpaTransactionManager} and {@link EntityManagerFactory}. Note that there could of course be some deduplication
|
||||
* with {@link example.springdata.jpa.multipleds.customer.CustomerConfig}. I just decided to keep it to focus on the
|
||||
* sepeartion of the two. Also, some overlaps might not even occur in real world scenarios (whether to create DDl or the
|
||||
* separation of the two. Also, some overlaps might not even occur in real world scenarios (whether to create DDl or the
|
||||
* like).
|
||||
*
|
||||
* @author Oliver Gierke
|
||||
|
||||
Reference in New Issue
Block a user