Skip to content

Fix README accuracy and tidy docs/code comments - #5

Merged
adharshvenkat merged 3 commits into
mainfrom
chore/readme-accuracy-and-style
Jul 3, 2026
Merged

Fix README accuracy and tidy docs/code comments#5
adharshvenkat merged 3 commits into
mainfrom
chore/readme-accuracy-and-style

Conversation

@adharshvenkat

Copy link
Copy Markdown
Owner
  • The intro said the whole stack runs in docker compose up; it doesn't.
    The naturalnav service's default command only starts the planner, executor,
    and detector, not Gazebo/Nav2. Rewritten to describe the actual setup.
  • Dropped an unclear, non-functional sentence from the intro.
  • General prose and formatting cleanup across README, Dockerfile,
    docker-compose.yml, and code comments/docstrings. No functional changes.

- The intro said the whole stack runs in `docker compose up`; it doesn't.
  The naturalnav service's default command only starts the planner, executor,
  and detector, not Gazebo/Nav2. Rewritten to describe the actual setup.
- Dropped an unclear, non-functional sentence from the intro.
- General prose and punctuation cleanup across README, Dockerfile,
  docker-compose.yml, and code comments/docstrings. No functional changes.
Decorative box-drawing dividers replaced with plain comments across
fleet_orchestrator.py, llm_planner.py, semantic_detector.py, Dockerfile,
docker-compose.yml, and the legacy world file. No functional changes.
@adharshvenkat
adharshvenkat merged commit 87bfa38 into main Jul 3, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant