From 308248e3781ee8a9a8ac01373921c19eaeed93ce Mon Sep 17 00:00:00 2001
From: "pre-commit-ci[bot]"
 <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Date: Fri, 13 Sep 2024 02:57:47 +0000
Subject: [PATCH] style(pre-commit): autofix

---
 create-prs-to-update-vcs-repositories/README.md | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/create-prs-to-update-vcs-repositories/README.md b/create-prs-to-update-vcs-repositories/README.md
index 3fae317e..f28bad72 100644
--- a/create-prs-to-update-vcs-repositories/README.md
+++ b/create-prs-to-update-vcs-repositories/README.md
@@ -61,8 +61,9 @@ None.
 
 ## What kind of tags are handled
 
-- Monitors all vcs-imported repositories in the ```autoware.repos``` (if default) which have a version with regular expression pattern ```r'\b(?<![^\s])\d+\.\d+\.\d+(?![-\w.+])\b'``` (if default).
+- Monitors all vcs-imported repositories in the `autoware.repos` (if default) which have a version with regular expression pattern `r'\b(?<![^\s])\d+\.\d+\.\d+(?![-\w.+])\b'` (if default).
   - This pattern match/mismatches for the following examples:
+
 ```
         "0.0.1",                # match
         "0.1.0",                # match
@@ -83,19 +84,22 @@ None.
 ```
 
 ## What kind of version update is possible?
+
 - If there is a new version with pattern matched in the vcs-imported repositories, create a PR for each repository, respectively.
 - The valid/invalid version update cases are as follows:
   - Valid ones (PR must be created):
+
 ```
     0.0.1  =>  0.0.2
     1.1.1  =>  1.2.1
     2.4.3  =>  3.0.0
 ```
 
-  - Invalid ones (PR is not created):
+- Invalid ones (PR is not created):
+
 ```
     main       =>  0.0.1
     v0.0.1     =>  0.0.2
     xxx-0.0.1  =>  0.0.9
     0.0.1-rc1  =>  0.0.2
-```
\ No newline at end of file
+```