chore: address pr comments and refine readme content

Author: keshavdandeva

google-cloud-bigquery-jdbc/README.MD

@@ -14,28 +14,25 @@ Java idiomatic client for [BigQuery JDBC][product-docs].
 
 If you are using Maven, add this to your pom.xml file:
 
-<!-- {x-version-update-start:google-cloud-bigquery-jdbc:released} -->
-
 ```xml
 <dependency>
   <groupId>com.google.cloud</groupId>
   <artifactId>google-cloud-bigquery-jdbc</artifactId>
-  <version>0.1.0-SNAPSHOT</version>
+  <version><version></version>
 </dependency>
 ```
 
 If you are using Gradle without BOM, add this to your dependencies:
 
 ```Groovy
-implementation 'com.google.cloud:google-cloud-bigquery-jdbc:0.1.0-SNAPSHOT'
+implementation 'com.google.cloud:google-cloud-bigquery-jdbc:<version>'
 ```
 
 If you are using SBT, add this to your dependencies:
 
 ```Scala
-libraryDependencies += "com.google.cloud" % "google-cloud-bigquery-jdbc" % "0.1.0-SNAPSHOT"
+libraryDependencies += "com.google.cloud" % "google-cloud-bigquery-jdbc" % "<version>"
 ```
-<!-- {x-version-update-end} -->
 
 ## Authentication
 
@@ -54,8 +51,7 @@ You need to have either Java with Maven installed or Docker. You might want to i
 ### Setup
 
 `make install` primarily relies on `mvn install` command. All following commands are primarily applicable for the `google-cloud-bigquery-jdbc` project.
-
-`bigquery-external-jdbc-tests` at this moment is independent and has its own configuration. 
+You can also use `make clean` to clean the project and `make lint` to format the code.
 
 ### Running tests
 
@@ -75,7 +71,7 @@ Example: `make unittest test=BigQueryArrowStructTest`
 
 #### Integration tests
 
-IMPORTANT: Running integration tests will skip unit tests. Primary focus of this command is to run specific set of tests without a lot of overhead.
+IMPORTANT: Running integration tests will skip unit tests by default. To include unit tests, run `make integration-test skipSurefire=false`. Primary focus of this command is to run specific set of tests without a lot of overhead.
 
 Majority of Integration tests rely on certain environment variables:
 
@@ -125,36 +121,26 @@ All Docker commands rely only on `GOOGLE_APPLICATION_CREDENTIALS` env being pres
 
 ### Packaging
 
-There are two ways to package Google JDBC Driver: thin jar and jar with all dependencies.
+There are a few ways to package the Google JDBC Driver. The output of the packaging commands can be found in the `target` directory.
+
+`make package` or `make docker-package` will create both a thin jar and a zip file with all dependencies.
+`make package-all-dependencies` or `make docker-package-all-dependencies` will create a single jar with all dependencies included.
+`make package-all-dependencies-shaded` or `make docker-package-all-dependencies-shaded` will create a single shaded jar with all dependencies included.
 
 #### Thin jar
 
-Thin jar can be generated by running `make docker-package`. It generates jar and list of dependencies in format compatible with copying into `pom.xml` file.
+The thin jar is created with `make package`. The thin jar is packaged as a zip file with its dependencies listed in a `dependencies.txt` file, compatible with `pom.xml`.
 
 #### All dependencies
 
-Jar with all dependencies can be generated by running `make docker-package-all-dependencies`. Produced jar includes all depenencies and can be used as a standalon jar with tools like R-Studio.
+The jar with all dependencies is also created. This jar includes all dependencies and can be used as a standalone jar with tools like R-Studio. You can run `make package-all-dependencies` or `make docker-package-all-dependencies` to build only the jar with all dependencies.
 
-### Custom query tests
+#### Shaded Jar
+You can also build a shaded jar with all dependencies. This can be done by running `make package-all-dependencies-shaded` or `make docker-package-all-dependencies-shaded`.
 
-Thin client using JDBC driver can be found in 'bigquery-jdbc-test-client' folder. It allows you to run custom queries with custom connection string to generate logs or measure performance.
+### Nightly builds
 
-It can be built for Google JDBC drivers or any other JDBC drivers. For other JDBC drivers, you need to specify a version and it will download it.
-
-#### Google test
-
-For Google, you need to build an uber jar following previous steps. When it is ready, you can use these
-sample commands to run it:
-
-```
-cd bigquery-jdbc-test-client
-make docker-package-for-validation JDBC_JAR_PATH=<path-to-uber-jar>
-make run QUERY=small
-```
-
-### Night builds
-
-Nightly build is running full set of Integration tests and extended Nightly tests that includes some long-running tests (takes 20+ minutes to complete).
+The nightly build runs the full set of integration tests, including the `ITBigQueryJDBCTest` and `ITNightlyBigQueryTest` test suites. It also includes some long-running tests (takes 20+ minutes to complete).
 
 Nightly Integration Tests include a step to build a full and thin jars and upload them to Google Storage.
 
@@ -173,7 +159,10 @@ Cloud Build Pipeline is uploading latest full jar to the internal location for p
 
 We're using [JaCoCo](https://www.eclemma.org/jacoco/) to track Code Coverage. `Makefile` has 2 separate set of commands for unittests and integration tests reports.
 
-You can run `make docker-coverage` and it will produce both results, you can find `jacoco-(unittest|full).zip` file in the root with results.
+You can run `make unit-test-coverage` to generate a coverage report for unit tests. The output will be in `jacoco-unittests.zip`.
+You can run `make full-coverage` to generate a coverage report for both unit and integration tests. The output will be in `jacoco-full.zip`.
+
+You can also run `make docker-coverage` which will produce both results. You can find `jacoco-unittests.zip` and `jacoco-full.zip` files in the root with results.
 
 ## Getting Started