Skip to content

Commit

Permalink
Remove reference-style markdown links from translated content (#7426)
Browse files Browse the repository at this point in the history
inline markdown links
  • Loading branch information
bmuenzenmeyer authored Jan 28, 2025
1 parent 3dce440 commit c119197
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 22 deletions.
17 changes: 5 additions & 12 deletions apps/site/pages/en/about/governance.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,31 +7,24 @@ layout: about

## Consensus Seeking Process

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

## Collaborators

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

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

For the current list of Collaborators, see the project's [README.md][].
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).

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

## Technical Steering Committee

The project is governed by the [Technical Steering Committee (TSC)][]
The project is governed by the [Technical Steering Committee (TSC)](https://github.com/nodejs/TSC/blob/main/TSC-Charter.md)
which is responsible for high-level guidance of the project. TSC is a
subset of active Collaborators who are nominated by other existing TSC
members.

[consensus seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
[readme.md]: https://github.com/nodejs/node/blob/main/README.md#current-project-team-members
[tsc]: https://github.com/nodejs/TSC
[technical steering committee (tsc)]: https://github.com/nodejs/TSC/blob/main/TSC-Charter.md
[collaborator-guide.md]: https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md
[nodejs/node]: https://github.com/nodejs/node
14 changes: 4 additions & 10 deletions apps/site/pages/en/about/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -53,12 +53,12 @@ synchronous methods of Node.js standard library. Because nothing blocks, scalabl
reasonable to develop in Node.js.

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

---

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

Node.js being designed without threads doesn't mean you can't take
advantage of multiple cores in your environment. Child processes can be spawned
by using our [`child_process.fork()`][] API, and are designed to be easy to
communicate with. Built upon that same interface is the [`cluster`][] module,
by using our [`child_process.fork()`](https://nodejs.org/api/child_process.html) API, and are designed to be easy to
communicate with. Built upon that same interface is the [`cluster`](https://nodejs.org/api/cluster.html) module,
which allows you to share sockets between processes to enable load balancing
over your cores.

[blocking vs. non-blocking]: /learn/asynchronous-work/overview-of-blocking-vs-non-blocking
[`child_process.fork()`]: https://nodejs.org/api/child_process.html
[`cluster`]: https://nodejs.org/api/cluster.html
[event machine]: https://github.com/eventmachine/eventmachine
[twisted]: https://twisted.org/

0 comments on commit c119197

Please sign in to comment.