Skip to content

Commit c119197

Browse files
Remove reference-style markdown links from translated content (#7426)
inline markdown links
1 parent 3dce440 commit c119197

File tree

2 files changed

+9
-22
lines changed

2 files changed

+9
-22
lines changed

apps/site/pages/en/about/governance.md

Lines changed: 5 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -7,31 +7,24 @@ layout: about
77

88
## Consensus Seeking Process
99

10-
The Node.js project follows a [Consensus Seeking][] decision making model.
10+
The Node.js project follows a [Consensus Seeking](https://en.wikipedia.org/wiki/Consensus-seeking_decision-making) decision making model.
1111

1212
## Collaborators
1313

14-
The [nodejs/node][] core GitHub repository is maintained by the Collaborators
14+
The [nodejs/node](https://github.com/nodejs/node) core GitHub repository is maintained by the Collaborators
1515
who are nominated by other existing Collaborators on an ongoing basis.
1616

1717
Individuals making significant and valuable contributions are made Collaborators
1818
and given commit-access to the project. These individuals are identified by other
1919
Collaborators and their nomination is discussed with the existing Collaborators.
2020

21-
For the current list of Collaborators, see the project's [README.md][].
21+
For the current list of Collaborators, see the project's [README.md](https://github.com/nodejs/node/blob/main/README.md#current-project-team-members).
2222

23-
A guide for Collaborators is maintained at [collaborator-guide.md][].
23+
A guide for Collaborators is maintained at [collaborator-guide.md](https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md).
2424

2525
## Technical Steering Committee
2626

27-
The project is governed by the [Technical Steering Committee (TSC)][]
27+
The project is governed by the [Technical Steering Committee (TSC)](https://github.com/nodejs/TSC/blob/main/TSC-Charter.md)
2828
which is responsible for high-level guidance of the project. TSC is a
2929
subset of active Collaborators who are nominated by other existing TSC
3030
members.
31-
32-
[consensus seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
33-
[readme.md]: https://github.com/nodejs/node/blob/main/README.md#current-project-team-members
34-
[tsc]: https://github.com/nodejs/TSC
35-
[technical steering committee (tsc)]: https://github.com/nodejs/TSC/blob/main/TSC-Charter.md
36-
[collaborator-guide.md]: https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md
37-
[nodejs/node]: https://github.com/nodejs/node

apps/site/pages/en/about/index.mdx

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -53,12 +53,12 @@ synchronous methods of Node.js standard library. Because nothing blocks, scalabl
5353
reasonable to develop in Node.js.
5454

5555
If some of this language is unfamiliar, there is a full article on
56-
[Blocking vs. Non-Blocking][].
56+
[Blocking vs. Non-Blocking](/learn/asynchronous-work/overview-of-blocking-vs-non-blocking).
5757

5858
---
5959

6060
Node.js is similar in design to, and influenced by, systems like Ruby's
61-
[Event Machine][] and Python's [Twisted][]. Node.js takes the event model a bit
61+
[Event Machine](https://github.com/eventmachine/eventmachine) and Python's [Twisted](https://twisted.org/). Node.js takes the event model a bit
6262
further. It presents an event loop as a runtime construct instead of as a library. In other systems,
6363
there is always a blocking call to start the event-loop.
6464
Typically, behavior is defined through callbacks at the beginning of a script, and
@@ -73,13 +73,7 @@ library or framework.
7373

7474
Node.js being designed without threads doesn't mean you can't take
7575
advantage of multiple cores in your environment. Child processes can be spawned
76-
by using our [`child_process.fork()`][] API, and are designed to be easy to
77-
communicate with. Built upon that same interface is the [`cluster`][] module,
76+
by using our [`child_process.fork()`](https://nodejs.org/api/child_process.html) API, and are designed to be easy to
77+
communicate with. Built upon that same interface is the [`cluster`](https://nodejs.org/api/cluster.html) module,
7878
which allows you to share sockets between processes to enable load balancing
7979
over your cores.
80-
81-
[blocking vs. non-blocking]: /learn/asynchronous-work/overview-of-blocking-vs-non-blocking
82-
[`child_process.fork()`]: https://nodejs.org/api/child_process.html
83-
[`cluster`]: https://nodejs.org/api/cluster.html
84-
[event machine]: https://github.com/eventmachine/eventmachine
85-
[twisted]: https://twisted.org/

0 commit comments

Comments
 (0)