Fix typo in project resource documentation #173
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
|
@grig777 Thanks for the PR. I think this section/line of the doc is out-of-date. I can't find it in the code either. This is likely due to the fact that While your PR is correct, I think I need to give all the resource docs a once over to ensure everything is up-to-dated. |
alexhung
approved these changes
Nov 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have identified and fixed a typo in the documentation file project.md. This file appears to be autogenerated by the terraform-plugin-docs plugin, but I wasn't able to determine the exact source of the typo from the code base. As a result, I made a direct modification to the markdown file.
If this is not the correct way to address this issue and the typo should instead be fixed from the original source that generates the file, I fully understand. Please feel free to close this PR, and open a new one with the correct fix.