8000 fix a wrong link · ilesinge/jsdoc.github.io@c8d792b · GitHub
[go: up one dir, main page]

Skip to content

Commit c8d792b

Browse files
committed
fix a wrong link
1 parent 0d3bd8d commit c8d792b

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

content/en/tags-param.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The parameter type can be a built-in JavaScript type, such as `string` or `Objec
2222
[JSDoc namepath][namepath] to another symbol in your code. If you have written documentation for the
2323
symbol at that namepath, JSDoc will automatically link to the documentation for that symbol. You can
2424
also use a type expression to indicate, for example, that a parameter is not nullable or can accept
25-
any type; see the [`@type` tag documentation][tags-type] for details.
25+
any type; see the [`@type` tag documentation][type-tag] for details.
2626

2727
If you provide a description, you can make the JSDoc comment more readable by inserting a hyphen
2828
before the description. Be sure to include a space before and after the hyphen.

tags-param.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ <h2 id="overview">Overview</h2>
7070
<p>The parameter type can be a built-in JavaScript type, such as <code>string</code> or <code>Object</code>, or a
7171
<a href="about-namepaths.html">JSDoc namepath</a> to another symbol in your code. If you have written documentation for the symbol at that namepath, JSDoc
7272
will automatically link to the documentation for that symbol. You can also use a type expression to indicate, for example, that a parameter is not nullable
73-
or can accept any type; see the [<code>@type</code> tag documentation][tags-type] for details.</p>
73+
or can accept any type; see the <a href="tags-type.html"><code>@type</code> tag documentation</a> for details.</p>
7474
<p>If you provide a description, you can make the JSDoc comment more readable by inserting a hyphen before the description. Be sure to include a space before and
7575
after the hyphen.</p>
7676
<h2 id="examples">Examples</h2>

0 commit comments

Comments
 (0)
0