change the structure of readme.md

Author: Bala-Sakabattula

README.md

@@ -44,26 +44,6 @@ Sync2Jira is a service that listens to activity on upstream GitHub repositories
 - GitHub API token
 - Fedora messaging environment (for production)
 
-### Using Docker
-
-```bash
-# Basic usage - run the sync service
-docker run -v /path/to/your/config:/etc/fedmsg.d/ \
-           -e GITHUB_TOKEN=your_token \
-           -e JIRA_TOKEN=your_jira_token \
-           quay.io/redhat-services-prod/sync2jira/sync2jira:latest
-
-# With initialization (sync all existing issues)
-docker run -v /path/to/your/config:/etc/fedmsg.d/ \
-           -e GITHUB_TOKEN=your_token \
-           -e JIRA_TOKEN=your_jira_token \
-           -e INITIALIZE=1 \
-           quay.io/redhat-services-prod/sync2jira/sync2jira:latest
-           
-```
-
-**Note**: The `-v /path/to/your/config:/etc/fedmsg.d/` option mounts your local configuration directory inside the container, allowing the containerized application to use your host system's configuration files.
-
 ### From Source
 
 ```bash
@@ -88,6 +68,8 @@ INITIALIZE=1 sync2jira
 sync2jira
 ```
 
+**Note**: Container images are also available as an alternative to native installation. See the [Usage](#usage) section for container deployment instructions.
+
 ## Configuration
 
 Create a configuration file in the `fedmsg.d/` directory. Here's a basic example:
@@ -152,24 +134,49 @@ config = {
 
 ## Usage
 
-### Container Deployment
+### Sync2Jira Service
+
+The main synchronization service that listens for GitHub events and creates/updates JIRA issues.
 
-**Sync Page UI**
+#### Native Installation
 
 ```bash
-# Run the web interface for manual synchronization
+# Run the service
+sync2jira
+
+# With initialization (sync all existing issues)
+INITIALIZE=1 sync2jira
+
+# Testing mode (dry run)
+# Set testing: True in config file
+sync2jira
+```
+
+#### Container Deployment
+
+```bash
+# Basic usage - run the sync service
 docker run -v /path/to/your/config:/etc/fedmsg.d/ \
-           -p 5000:5000 \
            -e GITHUB_TOKEN=your_token \
            -e JIRA_TOKEN=your_jira_token \
-           quay.io/redhat-aqe/sync2jira:sync-page
+           quay.io/redhat-services-prod/sync2jira/sync2jira:latest
+
+# With initialization (sync all existing issues)
+docker run -v /path/to/your/config:/etc/fedmsg.d/ \
+           -e GITHUB_TOKEN=your_token \
+           -e JIRA_TOKEN=your_jira_token \
+           -e INITIALIZE=1 \
+           quay.io/redhat-services-prod/sync2jira/sync2jira:latest
 ```
 
-### Manual Sync Interface
+**Note**: The `-v /path/to/your/config:/etc/fedmsg.d/` option mounts your local configuration directory inside the container, allowing the containerized application to use your host system's configuration files.
+
+### Sync Page UI
+
+A web interface for manually triggering synchronization of specific repositories when needed.
 
-The sync page is a separate web application that provides a UI for manually triggering synchronization.
+#### Native Installation
 
-**Running the sync page locally:**
 ```bash
 # Navigate to the sync-page directory
 cd sync-page
@@ -178,18 +185,32 @@ cd sync-page
 python event-handler.py
 ```
 
+#### Container Deployment
+
+```bash
+# Run the web interface for manual synchronization
+docker run -v /path/to/your/config:/etc/fedmsg.d/ \
+           -p 5000:5000 \
+           -e GITHUB_TOKEN=your_token \
+           -e JIRA_TOKEN=your_jira_token \
+           quay.io/redhat-aqe/sync2jira:sync-page
+```
+
 **Access the interface:**
 - Local development: `http://localhost:5000` (or whatever port Flask shows)
 - Production: Configure according to your deployment environment
 
-
 ### Environment Variables
 
-- `INITIALIZE`: Set to `1` to perform initial sync of all issues
-- `FEDORA_MESSAGING_QUEUE`: Custom message queue name
+The following environment variables can be used to configure both tools:
+
+**Common Variables (used by both sync2jira and sync-page):**
 - `GITHUB_TOKEN`: GitHub API token (can override config)
 - `JIRA_TOKEN`: JIRA API token (can override config)
 
+**Sync2Jira Service Only:**
+- `INITIALIZE`: Set to `1` to perform initial sync of all issues
+- `FEDORA_MESSAGING_QUEUE`: Custom message queue name
 
 ## Documentation