Updated README.md (#1778)

tj-actions-bot · jackton1 · web-flow · commit 04c00459a27a · 2023-12-07T03:56:05.000Z
Co-authored-by: jackton1 &lt;jackton1@users.noreply.github.com&gt;
diff --git a/README.md b/README.md
@@ -609,10 +609,9 @@ Support this project with a :star:
 
 > \[!IMPORTANT]
 >
-> * When using `files_yaml*` inputs, it's important to prefix all outputs with the key to ensure that the correct outputs are accessible.
+> *   When using `files_yaml*` inputs, it's important to prefix all outputs with the key to ensure that the correct outputs are accessible.
 >
->   For example, if you use `test` as the key, you can access outputs like `added_files`, `any_changed`, and so on by prefixing them with the key `test_added_files` or `test_any_changed` etc.
-
+>     For example, if you use `test` as the key, you can access outputs like `added_files`, `any_changed`, and so on by prefixing them with the key `test_added_files` or `test_any_changed` etc.
 
 ## Outputs 📤
 

Original file line number	Diff line number	Diff line change
`@@ -609,10 +609,9 @@ Support this project with a :star:`
`609`	`609`
`610`	`610`	`> \[!IMPORTANT]`
`611`	`611`	`>`
`612`		-> * When using `files_yaml*` inputs, it's important to prefix all outputs with the key to ensure that the correct outputs are accessible.
	`612`	+> * When using `files_yaml*` inputs, it's important to prefix all outputs with the key to ensure that the correct outputs are accessible.
`613`	`613`	`>`
`614`		-> For example, if you use `test` as the key, you can access outputs like `added_files`, `any_changed`, and so on by prefixing them with the key `test_added_files` or `test_any_changed` etc.
`615`		`-`
	`614`	+> For example, if you use `test` as the key, you can access outputs like `added_files`, `any_changed`, and so on by prefixing them with the key `test_added_files` or `test_any_changed` etc.
`616`	`615`
`617`	`616`	`## Outputs 📤`
`618`	`617`