diff --git a/docs/en/next/doc-markdown.html b/docs/en/next/doc-markdown.html index 9377022bc7..1f6602293a 100644 --- a/docs/en/next/doc-markdown.html +++ b/docs/en/next/doc-markdown.html @@ -109,7 +109,7 @@

Generating Table of Contents

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

-

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Write your documentation using h3 headers for each function inside a code block. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

In your markdown file, insert a line with the text ``. Write your documentation using h3 headers for each function inside a code block. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

Example:

### `docusaurus.function(a, b)`
 
diff --git a/docs/en/next/doc-markdown/index.html b/docs/en/next/doc-markdown/index.html
index 9377022bc7..1f6602293a 100644
--- a/docs/en/next/doc-markdown/index.html
+++ b/docs/en/next/doc-markdown/index.html
@@ -109,7 +109,7 @@
 

Generating Table of Contents

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

-

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Write your documentation using h3 headers for each function inside a code block. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

In your markdown file, insert a line with the text ``. Write your documentation using h3 headers for each function inside a code block. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

Example:

### `docusaurus.function(a, b)`
 
diff --git a/docs/es-ES/next/doc-markdown.html b/docs/es-ES/next/doc-markdown.html
index 39266b220e..e15374fe6e 100644
--- a/docs/es-ES/next/doc-markdown.html
+++ b/docs/es-ES/next/doc-markdown.html
@@ -103,7 +103,7 @@
 

Generar tabla de contenidos

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

-

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

In your markdown file, insert a line with the text ``. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

Ejemplo:

### `docusaurus.function(a, b)`
 
diff --git a/docs/es-ES/next/doc-markdown/index.html b/docs/es-ES/next/doc-markdown/index.html
index 39266b220e..e15374fe6e 100644
--- a/docs/es-ES/next/doc-markdown/index.html
+++ b/docs/es-ES/next/doc-markdown/index.html
@@ -103,7 +103,7 @@
 

Generar tabla de contenidos

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

-

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

In your markdown file, insert a line with the text ``. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

Ejemplo:

### `docusaurus.function(a, b)`
 
diff --git a/docs/ro/next/doc-markdown.html b/docs/ro/next/doc-markdown.html
index 53dfcf35ab..2ffda17c52 100644
--- a/docs/ro/next/doc-markdown.html
+++ b/docs/ro/next/doc-markdown.html
@@ -109,7 +109,7 @@
 

Generând Cuprinsul

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

-

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Scrie-ți documentația folosind header-e h3 pentru fiecare funcție în interiorul unui bloc de cod. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

In your markdown file, insert a line with the text ``. Scrie-ți documentația folosind header-e h3 pentru fiecare funcție în interiorul unui bloc de cod. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

Exemplu:

### `docusaurus.function(a, b)`
 
diff --git a/docs/ro/next/doc-markdown/index.html b/docs/ro/next/doc-markdown/index.html
index 53dfcf35ab..2ffda17c52 100644
--- a/docs/ro/next/doc-markdown/index.html
+++ b/docs/ro/next/doc-markdown/index.html
@@ -109,7 +109,7 @@
 

Generând Cuprinsul

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

-

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Scrie-ți documentația folosind header-e h3 pentru fiecare funcție în interiorul unui bloc de cod. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

In your markdown file, insert a line with the text ``. Scrie-ți documentația folosind header-e h3 pentru fiecare funcție în interiorul unui bloc de cod. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

Exemplu:

### `docusaurus.function(a, b)`
 
diff --git a/docs/tr/next/doc-markdown.html b/docs/tr/next/doc-markdown.html
index d45fbc6bf9..9e211e0224 100644
--- a/docs/tr/next/doc-markdown.html
+++ b/docs/tr/next/doc-markdown.html
@@ -109,7 +109,7 @@
 

İçerik Panosu Üretme

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

-

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

In your markdown file, insert a line with the text ``. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

Örnek:

### `docusaurus.function(a, b)`
 
diff --git a/docs/tr/next/doc-markdown/index.html b/docs/tr/next/doc-markdown/index.html
index d45fbc6bf9..9e211e0224 100644
--- a/docs/tr/next/doc-markdown/index.html
+++ b/docs/tr/next/doc-markdown/index.html
@@ -109,7 +109,7 @@
 

İçerik Panosu Üretme

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

-

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

In your markdown file, insert a line with the text ``. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

Örnek:

### `docusaurus.function(a, b)`
 
diff --git a/docs/zh-CN/next/doc-markdown.html b/docs/zh-CN/next/doc-markdown.html
index 87988d5204..798a799a53 100644
--- a/docs/zh-CN/next/doc-markdown.html
+++ b/docs/zh-CN/next/doc-markdown.html
@@ -109,7 +109,7 @@
 

生成目录

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

-

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

In your markdown file, insert a line with the text ``. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

例如:

### `docusaurus.function(a, b)`
 
diff --git a/docs/zh-CN/next/doc-markdown/index.html b/docs/zh-CN/next/doc-markdown/index.html
index 87988d5204..798a799a53 100644
--- a/docs/zh-CN/next/doc-markdown/index.html
+++ b/docs/zh-CN/next/doc-markdown/index.html
@@ -109,7 +109,7 @@
 

生成目录

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

-

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

In your markdown file, insert a line with the text ``. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

例如:

### `docusaurus.function(a, b)`