You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openjpa.apache.org by il...@apache.org on 2020/09/16 08:32:51 UTC

[openjpa] branch master updated: Update README.adoc (#73)

This is an automated email from the ASF dual-hosted git repository.

ilgrosso pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/openjpa.git


The following commit(s) were added to refs/heads/master by this push:
     new 325af83  Update README.adoc (#73)
325af83 is described below

commit 325af839651dc5c16ae7781651b4702fead7b1dc
Author: PoojaChandak <po...@gmail.com>
AuthorDate: Wed Sep 16 14:02:40 2020 +0530

    Update README.adoc (#73)
    
    minor grammatical/typo changes
---
 README.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.adoc b/README.adoc
index d8c8643..1dc2d2e 100644
--- a/README.adoc
+++ b/README.adoc
@@ -32,8 +32,8 @@ The best way to compile Apache OpenJPA yourself is to run the build against the
 
 The Apache OpenJPA project also contains a setup for testing against multiple databases.
 The easiest way is to use Docker.
-We assume that Docker is installed to be used from your current user.
-The respective database image has to be started manually bofore starting the build.
+We assume that Docker is installed to be used by your current user.
+The respective database image has to be started manually before starting the build.
 The reason for not starting it as part of the build itself is to be able to look at the database content after the build did run.
 
 To start e.g. a PostgreSQL Docker image you can simply invoke the following command.
@@ -42,7 +42,7 @@ This is used because the docker container is configured only at the root project
 
  mvn -N -Ptest-mysql-docker docker:start
 
-After that you can execute your tests with the respective Maven profile
+After that, you can execute your tests with the respective Maven profile
 
  mvn clean install -Ptest-mysql-docker