Fix typo on new account setup page for developers #223
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
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.
Hi!
I've been interested in building some API clients for the Procore API (.NET and PHP) and noticed a typo. I've just recently been going through the documentation and wanted to continually improve bits and pieces where I can. I'm not associated with Procore, just a curious developer interested in construction software.
Side note, I noticed a few issues getting setup with the repo. It looks like with the version of Jekyll powering the docs, there's some issues when using Ruby versions >= 3.0. I think it would be helpful for folks like myself looking to contribute to note somewhere in the contributing docs which version of Ruby we should be targeting. Currently targeting 2.7.8 locally with rbenv, though not including the pinned file as to not cause issues for the internal devs at Procore working on the docs.