Feat: Updates readme and a few nitpicks

[deependujha]

Before submitting

• Was this discussed/agreed via a Github issue? (no need for typos and docs improvements)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure to update the docs?
• Did you write any new necessary tests?

What does this PR do?

• Readme updated for Distributed Optimize function
  and, a few nitpicks

PR review

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in GitHub issues there's a high chance it will not be merged.

Did you have fun?

Make sure you had fun coding 🙃

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Please upload report for BASE (main@df8dcd1). Learn more about missing BASE report.

Additional details and impacted files

@@          Coverage Diff          @@
##             main   #223   +/-   ##
=====================================
  Coverage        ?    77%           
=====================================
  Files           ?     33           
  Lines           ?   4695           
  Branches        ?      0           
=====================================
  Hits            ?   3621           
  Misses          ?   1074           
  Partials        ?      0           

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
5685611	Triggered	Generic High Entropy Secret	84dce3d	tests/streaming/test_resolver.py	View secret
5685611	Triggered	Generic High Entropy Secret	84dce3d	tests/streaming/test_resolver.py	View secret
5685611	Triggered	Generic High Entropy Secret	84dce3d	tests/streaming/test_resolver.py	View secret
5685611	Triggered	Generic High Entropy Secret	84dce3d	tests/streaming/test_resolver.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[awaelchli]

Why was this number changed @deependujha?
This example was constructed in a specific way.

[tchaton]

@deependujha Unfortunately, we found another core issue and this seemed to be a legit test failure. @awaelchli is working on it.