SK-2415 Addressed review comments

Author: skyflow-himanshu

README.md

@@ -128,7 +128,7 @@ config = {
 }
 
 # Initialize Skyflow client
-client = (
+skyflow_client = (
     Skyflow.builder()
     .add_vault_config(config)
     .set_log_level(LogLevel.ERROR)
@@ -164,7 +164,7 @@ insert_response = skyflow_client.vault('<VAULT_ID>').insert(insert_request)
 print('Insert response:', insert_response)
 ```
 
-## Upgrade from V1 to V2
+## Upgrade from v1 to v2
 
 Upgrade from `skyflow-python` v1 using the dedicated guide in [docs/migrate_to_v2.md](docs/migrate_to_v2.md).
 
@@ -646,6 +646,8 @@ The SDK accepts one of several types of credentials object.
    JSON-formatted string containing service account credentials. Use when integrating with secret management systems or when credentials are passed programmatically.
 
    ```python
+   import os
+
    credentials = {
     "credentials_string": os.getenv("SKYFLOW_CREDENTIALS")
     }
@@ -717,7 +719,7 @@ Digitally sign data tokens with a service account's private key to add an extra
 
 ## Logging
 
-The  SDK provides logging using python's inbuilt `logging` library. By default the logging level of the SDK is set to `LogLevel.ERROR`. This can be changed by using `set_log_level(log_level)` as shown below:
+The SDK provides logging using Python's inbuilt `logging` library. By default the logging level of the SDK is set to `LogLevel.ERROR`. This can be changed by using `set_log_level(log_level)` as shown below:
 
 Currently, the following five log levels are supported:
 
@@ -737,7 +739,15 @@ When `LogLevel.ERROR` is passed, only ERROR logs will be printed.
 ### Example: Setting LogLevel to INFO
 
 ```python
-from skyflow import Skyflow, LogLevel
+from skyflow import Skyflow, LogLevel, Env
+
+# Define vault configuration
+vault_config = {
+    'vault_id': '<VAULT_ID>',
+    'cluster_id': '<CLUSTER_ID>',
+    'env': Env.PROD,
+    'credentials': {'api_key': '<API_KEY>'}
+}
 
 skyflow_client = (
     Skyflow.builder()
@@ -754,6 +764,8 @@ skyflow_client = (
 Wrap your calls to the Skyflow SDK in try/except blocks as a best practice. Use the `SkyflowError` class to identify errors coming from Skyflow versus general request/response errors.
 
 ```python
+from skyflow.error import SkyflowError
+
 try:
     # ...call the Skyflow SDK
     pass

docs/auth_credentials.md

@@ -1,6 +1,6 @@
 # Authentication credentials options
 
-> **Note:** Only one type of credential can be used at a time. If multiple credentials are provided, the order of precedence depends on how they are passed to the configuration.
+> **Note:** Only one type of credential can be used at a time. If multiple credentials are provided, the last one added takes precedence.
 
 1. **API keys**
    A unique identifier used to authenticate and authorize requests to an API.
@@ -41,4 +41,4 @@
    ```
 
 5. **Environment variables**
-   If no credentials are explicitly provided the SDK automatically looks for the SKYFLOW_CREDENTIALS environment variable. This variable must return an object like one of the examples above.
+   If no credentials are explicitly provided, the SDK automatically looks for the `SKYFLOW_CREDENTIALS` environment variable. This variable must contain a JSON string like one of the examples above.

docs/migrate_to_v2.md

@@ -1,10 +1,10 @@
-# Migrate from V1 to V2
+# Migrate from v1 to v2
 
-This guide outlines the steps required to migrate the Skyflow Python SDK from version 1 (V1) to version 2 (V2).
+This guide outlines the steps required to migrate the Skyflow Python SDK from version 1 (v1) to version 2 (v2).
 
 ## Authentication
 
-In V2, multiple authentication options have been introduced. You can now provide credentials in the following ways:
+In v2, multiple authentication options have been introduced. You can now provide credentials in the following ways:
 
 - **Passing credentials in ENV** (`SKYFLOW_CREDENTIALS`) (**Recommended**)
 - **API Key**
@@ -14,7 +14,7 @@ In V2, multiple authentication options have been introduced. You can now provide
 
 These options allow you to choose the authentication method that best suits your use case.
 
-### V1 (Old): Passing the token provider function below as a parameter to the Configuration.
+### v1 (Old): Passing the token provider function below as a parameter to the Configuration.
 
 ```python
 # User defined function to provide access token to the vault apis
@@ -26,7 +26,7 @@ def token_provider():
     return bearer_token
 ```
 
-#### V2 (New): Passing one of the following:
+#### v2 (New): Passing one of the following:
 
 ```python
 # Option 1: API Key (Recommended)
@@ -60,23 +60,23 @@ credentials = {
 
 ### Initializing the client
 
-In V2, we have introduced a Builder design pattern for client initialization and added support for multi-vault. This allows you to configure multiple vaults during client initialization. 
+In v2, we have introduced a Builder design pattern for client initialization and added support for multi-vault. This allows you to configure multiple vaults during client initialization. 
 
 During client initialization, you can pass the following parameters:
 
 - **`vault_id`** and **`cluster_id`**: These values are derived from the vault ID & vault URL.
 - **`env`**: Specify the environment (e.g., SANDBOX or PROD).
 - **`credentials`**: The necessary authentication credentials.
 
-#### V1 (Old):
+#### v1 (Old):
 
 ```python
 # Initializing a Skyflow Client instance with a SkyflowConfiguration object
 config = Configuration('<VAULT_ID>', '<VAULT_URL>', token_provider)
 client = Client(config)
 ```
 
-#### V2 (New):
+#### v2 (New):
 
 ```python
 # Initializing a Skyflow Client instance
@@ -101,14 +101,14 @@ client = (
 
 ### Request & Response Structure
 
-In V2, with the introduction of constructor parameters, you can now pass parameters to `InsertRequest`. This request needs 
+In v2, with the introduction of constructor parameters, you can now pass parameters to `InsertRequest`. This request needs 
 - **`table_name`**: The name of the table.
 - **`values`**: An array of objects containing the data to be inserted.
 The response will be of type `InsertResponse` class, which contains `inserted_fields` and errors.
 
 **Note:** Similar patterns apply to other operations like Get, Update, Delete. See the [README](../README.md) for complete examples.
 
-#### V1 (Old): Request Building
+#### v1 (Old): Request Building
 
 ```python
 client.insert(
@@ -127,9 +127,11 @@ client.insert(
 )
 ```
 
-#### V2 (New): Request Building
+#### v2 (New): Request Building
 
 ```python
+from skyflow.vault.data import InsertRequest
+
 # Prepare Insertion Data
 insert_data = [
    {
@@ -152,7 +154,7 @@ insert_request = InsertRequest(
 response = skyflow_client.vault(primary_vault_config.get('<VAULT_ID>')).insert(insert_request)
 ```
 
-#### V1 (Old): Response Structure
+#### v1 (Old): Response Structure
 
 ```json
 {
@@ -170,7 +172,7 @@ response = skyflow_client.vault(primary_vault_config.get('<VAULT_ID>')).insert(i
 }
 ```
 
-#### V2 (New): Response Structure
+#### v2 (New): Response Structure
 
 ```python
 InsertResponse(
@@ -186,40 +188,40 @@ InsertResponse(
 
 ### Request Options
 
-In V2, we have introduced constructor parameters, allowing you to set options as key-value pairs as parameters in request.
+In v2, we have introduced constructor parameters, allowing you to set options as key-value pairs as parameters in request.
 
-#### V1 (Old):
+#### v1 (Old):
 
 ```python
 options = InsertOptions(
     tokens = True
 )
 ```
 
-#### V2 (New):
+#### v2 (New):
 
 ```python
 insert_request = InsertRequest(
-   table=table_name,        # Replace with the table name
-   values=insert_data,
-   return_tokens=False,          # Do not return tokens
-   continue_on_error=False,      # Stop inserting if any record fails
-   upsert='<UPSERT_COLUMN>',     # Replace with the column name used for upsert logic
-   token_mode=TokenMode.DISABLE, # Disable BYOT
-   tokens='<TOKENS>'             # Replace with tokens when TokenMode is ENABLE.
+    table=table_name,             # Replace with the table name
+    values=insert_data,
+    return_tokens=False,          # Do not return tokens
+    continue_on_error=False,      # Stop inserting if any record fails
+    upsert='<UPSERT_COLUMN>',     # Replace with the column name used for upsert logic, if any
+    token_mode=TokenMode.DISABLE, # Disable BYOT
+    tokens='<TOKENS>'             # Set with tokens when TokenMode is ENABLE
 )
 ```
 
 ### Error Structure
 
-In V2, we have enriched the error details to provide better debugging capabilities. 
+In v2, we have enriched the error details to provide better debugging capabilities. 
 The error response now includes: 
 - **http_status**: The HTTP status code. 
 - **grpc_code**: The gRPC code associated with the error. 
 - **details** & **message**: A detailed description of the error. 
 - **request_id**: A unique request identifier for easier debugging.
 
-#### V1 (Old) Error Structure:
+#### v1 (Old) Error Structure:
 
 ```json
 {
@@ -228,7 +230,7 @@ The error response now includes:
 }
 ```
 
-#### V2 (New) Error Structure:
+#### v2 (New) Error Structure:
 
 ```python
 {