Bug: Missing next steps after deployment setup on Readme



Next steps after deployment setup on Readme are missing
diff --git a/README.md b/README.md
index 5b5518d31fc..72ac7e0e3a7 100644
--- a/README.md
+++ b/README.md
@@ -101,6 +101,13 @@ Check out the [local setup guide][local-setup-guide] for a more details on setti
 
 Attaching to hyperswitch-control-center-1, hyperswitch-server-1, hyperswitch-web-1, migration_runner-1, pg-1, redis-standalone-1
 ```
+You've now setup Hyperswitch in your local machine. In order to verify that the server is up and running hit the health endpoint:
+```shell
+curl --head --request GET 'http://localhost:8080/health'
+```
+The expected response here is a `200 OK` status code. This indicates that the server and all of its dependent services are functioning correctly.
+Now, you can access the Control Center in your browser at `http://localhost:9000`.
+The next step is to configure a connector with the Hyperswitch Control Center and try a payment.
 
 ### 2. Deployment on cloud
 

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [X] Documentation
- [ ] CI/CD

## Description
<!-- Describe your changes in detail -->
Updated next steps after deployment setup on Readme

### Additional Changes

- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables

<!--
Provide links to the files with corresponding changes.

Following are the paths where you can find config files:
1. `config`
2. `crates/router/src/configs`
3. `loadtest/config`
-->


## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.

If you don't have an issue, we'd recommend starting with one first so the PR
can focus on the implementation (unless it is an obvious bug or documentation fix
that will have little conversation).
-->
Updated next steps after deployment setup on Readme
closes : #7685 7685
## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screenshots)?
-->


## Checklist
<!-- Put an `x` in the boxes that apply -->

- [ ] I formatted the code `cargo +nightly fmt --all`
- [ ] I addressed lints thrown by `cargo clippy`
- [ ] I reviewed the submitted code
- [ ] I added unit tests for my changes where possible
