Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[do not merge] Testing vale capitalization #246

Closed
wants to merge 12 commits into from
Closed

Conversation

timothymcmackin
Copy link
Collaborator

No description provided.

@timothymcmackin timothymcmackin self-assigned this Jan 4, 2024
@timothymcmackin timothymcmackin requested a review from a team as a code owner January 4, 2024 15:54
Copy link

vercel bot commented Jan 4, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
docs-staging ✅ Ready (Inspect) Visit Preview Jan 4, 2024 5:00pm


This is the official Tezos implementation of Vale.

It is in a chapter and an article.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Tezos.Terms] Do not use the term 'chapter'


This is the official Tezos implementation of Vale.

It is in a chapter and an article.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Tezos.Terms] Do not use the term 'article'


It is in a chapter and an article.

We have l1 and l2, which is smart rollups.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[Tezos.Substitutions] Use 'layer 1' instead of 'l1'


It is in a chapter and an article.

We have l1 and l2, which is smart rollups.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[Tezos.Substitutions] Use 'layer 2' instead of 'l2'


We love smart rollups.

The term Smart Contracts should not be capitalized.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Tezos.DoNotCapitalize] Do not capitalize 'smart contract'


It is in a chapter and an article.

We have l1 and l2, which is smart rollups.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Tezos.Capitalize] Always capitalize 'Smart Rollups'


We have l1 and l2, which is smart rollups.

We love smart rollups.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Tezos.Capitalize] Always capitalize 'Smart Rollups'


The term Smart Contracts should not be capitalized.

What if I failed to capitalize smart rollups on a different line?
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Tezos.Capitalize] Always capitalize 'Smart Rollups'


What if I failed to capitalize smart rollups on a different line?

Adding another line about smart rollups.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Tezos.Capitalize] Always capitalize 'Smart Rollups'


Adding another line about smart rollups.

Some other things about smart rollups.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Tezos.Capitalize] Always capitalize 'Smart Rollups'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant