Fixed content by grammar rules

imCodePartnerAB · Aug 10, 2016 · 6914a93 · 6914a93
1 parent 8df30ca
commit 6914a93
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 8 deletions.
diff --git a/docs/basic_concepts/data_access.rst b/docs/basic_concepts/data_access.rst
@@ -1,11 +1,9 @@
 Data Access Layer
 =================
 
-Data access layer in iVIS implemented using JPA standard
-(ORM provider Hibernate).
+Data access layer in iVIS is implemented using standard JPA (using Hibernate as ORM provider).
 
-All tables present as mapping of entities.
-Tables have prefix "dbo_" that means database object,
+All entities are mapped to the corresponding tables. All tables (except authorization ones) have prefix "dbo_" that means "database object".
 Except of authorization tables
 (it relate with ideological considerations).
 
@@ -17,11 +15,11 @@ JPA classes located in *com.imcode.entities* of ivis-core module in iVIS project
 
 **JPA entities diagram** :download:`download <../images/jpaEntitiesDiagram.png>`.
 
-Relations in DB also implement by JPA standard.
+Relations in DB also are implement by standard JPA.
 
 .. note::
 
-    embeddables have not got id. Because they can not exist without entity
+    Embedded entities don't have id and cann't exist without parent entity.
 
 LIST OF ALL TABLES AND DESCRIPTION
 ----------------------------------

diff --git a/docs/basic_concepts/security_subsystem.rst b/docs/basic_concepts/security_subsystem.rst
@@ -1,8 +1,8 @@
 Security Subsystem
 ==================
 
-iVIS use `OAuth 2.0 <https://tools.ietf.org/html/rfc6749>`_ protocol
-(`Spring Security <http://projects.spring.io/spring-security/>`_ provider)
+iVIS uses `OAuth 2.0 <https://tools.ietf.org/html/rfc6749>`_ protocol
+(implemented by standard `Spring Security <http://projects.spring.io/spring-security/>`_ provider)
 
 The provider role in OAuth 2.0 is actually split between Authorization Service and Resource Service,
 and these reside in the iVIS with Spring Security OAuth.