[ 
https://issues.apache.org/jira/browse/CASSANDRA-17936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17936:
--------------------------------------
    Description: 
In the [Guardrails 
Framework|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html]
 blog post, the sentence:

{quote}
Continuing with the previous example, if we have a hard limit of ten tables 
({{tables_warn_threshold: 10}}) and we try ...
{quote}

should spell {{tables_fail_threshold}}  instead of {{tables_warn_threshold}} .

  was:
In the blog post about introduction of guardrails 
([https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html),]
 the sentence

_Continuing with the previous example, if we have a hard limit of ten tables 
({{{}tables_warn_threshold: 10{}}}) and we try [...]_

should spell {{tables_fail_threshold}}  instead of {{tables_warn_threshold}} .


> WEBSITE - Fix incorrect tables threshold mentioned in Guardrails blogpost
> -------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17936
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17936
>             Project: Cassandra
>          Issue Type: Task
>          Components: Documentation/Blog
>            Reporter: Stefano Lottini
>            Assignee: Erick Ramirez
>            Priority: Normal
>             Fix For: NA
>
>
> In the [Guardrails 
> Framework|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html]
>  blog post, the sentence:
> {quote}
> Continuing with the previous example, if we have a hard limit of ten tables 
> ({{tables_warn_threshold: 10}}) and we try ...
> {quote}
> should spell {{tables_fail_threshold}}  instead of {{tables_warn_threshold}} .



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to