several cosmetic fixes. (#21)

* several cosmetic fixes.

Signed-off-by: Tomoya Fujita <[email protected]>

* address review comments to roll back the changes.

Signed-off-by: Tomoya Fujita <[email protected]>

* remove unnecessary changes.

Signed-off-by: Tomoya.Fujita <[email protected]>

---------

Signed-off-by: Tomoya Fujita <[email protected]>
Signed-off-by: Tomoya.Fujita <[email protected]>

Author: Tomoya Fujita

.gitignore

@@ -8,6 +8,9 @@ Gemfile.lock
 .jekyll-metadata
 _site
 
+# Ruby LSP
+.ruby-lsp
+
 # RubyGems
 *.gem
 

README.md

@@ -1,10 +1,10 @@
 # Robotics Enhancement Proposals Official Source
 
-This repository is the offical source of the Robotics Enhancement Proposals (REP) of the Open Source Robotics Alliance Technical Governance Committee.
+This repository is the official source of the Robotics Enhancement Proposals (REP) of the Open Source Robotics Alliance Technical Governance Committee.
 
 # REP submission process
 
-On October 23rd, 2025 the [Open Source Robotics Alliance (OSRA)](https://osralliance.org/) Technical Governance Comittee (TGC) launched our new REP process.
+On October 23rd, 2025 the [Open Source Robotics Alliance (OSRA)](https://osralliance.org/) Technical Governance Committee (TGC) launched our new REP process.
 Details on how to submit new REPs can be found in [REP-0001:2025](https://reps.openrobotics.org/rep-0001-2025/).
 Additional details can be found in our [announcement on ROS Discourse](https://discourse.openrobotics.org/t/launch-of-the-osras-new-robotics-enhancement-proposal-rep-process/50668).
 The REP review process is significantly different from most conventional source code repositoires. **We recommend you read REP-0001:2025 in its entirety before [submitting a pull request.]((https://reps.openrobotics.org/rep-0001-2025/))**.
@@ -19,7 +19,7 @@ A specification of the REP numbering system can be [found in REP-0001:2025](http
 
 # REP template
 
-A template REP sumbission can be found in [REP-0004:2025 - Sample Markdown REP Template](https://github.com/openrobotics/reps/blob/main/_posts/rep-0004%3A2025.md).
+A template REP submission can be found in [REP-0004:2025 - Sample Markdown REP Template](https://github.com/openrobotics/reps/blob/main/_posts/rep-0004%3A2025.md).
 
 # Building locally
 

_posts/rep-0001:2025.md

@@ -159,7 +159,7 @@ The Lead Author should then follow the process below, with the assistance of the
 2. The Lead Author fills in the known header fields in their new file, as appropriate.
    Most importantly, the `REP:` field must be set to the same number as used in the filename, and the `Status:` field must be set to `Draft`.
    For full details, see the [REP Header](#rep-header) section, below.
-3. The Lead Author updates the `CODEOWNERS` file to list, for the new REP's directory, any co-authors or PMC Sponsors who are REP Editors (in other words, they have write access to the REP Repository).
+3. The Lead Author updates the `CODEOWNERS` file to list, for the new REP's path, any co-authors or PMC Sponsors who are REP Editors (in other words, they have write access to the REP Repository).
    This will allow those people to be automatically assigned to any pull requests that change the file.
 4. The Lead Author pushes their changes to the fork they created in step 1, and submits a pull request to the REP Repository.
 5. The REP Editors review the PR for general errors, confirming that the proposed REP meets the minimum readiness criteria.