doc: use code markup/markdown in headers in addons documentation · nodejs/node@b5a19bc · GitHub

nodejs / node Public

• Notifications You must be signed in to change notification settings
• Fork 36.6k
• Star 120k

• Code
• Issues 635
• Pull requests 755
• Actions
• Projects
• Security and quality
• Insights

Additional navigation options

Commit b5a19bc

Browse filesBrowse the repository at this point in the historyBrowse files

Trott

authored and

BethGriggs

committed

doc: use code markup/markdown in headers in addons documentation

Backport-PR-URL: #31108 PR-URL: #31086 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>

1 parent 135097f commit b5a19bc
Copy full SHA for b5a19bc

1 file changed

+1-1Lines changed: 1 addition & 1 deletion

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

• doc/api
  • addons.md

Expand file treeCollapse file tree

Open diff view settings

Collapse file

‎doc/api/addons.md‎

Copy file name to clipboardExpand all lines: doc/api/addons.md

+1-1Lines changed: 1 addition & 1 deletion

• Display the source diff
• Display the rich diff

Original file line number	Diff line number	Diff line change
@@ -346,7 +346,7 @@ only the symbols exported by Node.js will be available.
346	346	source image. Using this option, the Addon will have access to the full set of
347	347	dependencies.
348	348
349		- ### Loading Addons using require()
	349	+ ### Loading Addons using `require()`
350	350
351	351	The filename extension of the compiled Addon binary is `.node` (as opposed
352	352	to `.dll` or `.so`). The [`require()`][require] function is written to look for

0 commit comments

Comments

0 (0)