@@ -13,14 +13,14 @@ files][].
13
13
These instructions are for [ Gitpod.io] [ ] , adjust as needed for your favorite
14
14
cloud IDE:
15
15
16
- 1 . Fork this repo . For help, see [ Fork a repo ] [ fork ] .
16
+ 1 . Fork this repository . For help, see [ Fork a repository ] [ fork ] .
17
17
2 . From [ gitpod.io/workspaces] [ ] , create a new workspace (do this only once) or
18
18
open an existing workspace over your fork. You can also visit a link of the
19
19
form:
20
20
< https://gitpod.io#https://github.com/YOUR_GITHUB_ID/opentelemetry.io > .
21
21
22
- > ** Note** : If you have the necessary permissions to work from this repo, or
23
- > just want to look around, open
22
+ > ** Note** : If you have the necessary permissions to work from this
23
+ > repository, or just want to look around, open
24
24
> < https://gitpod.io/#https://github.com/open-telemetry/opentelemetry.io > .
25
25
26
26
Gitpod will automatically install the repo-specific packages for you. You're now
29
29
30
30
### Local setup
31
31
32
- 1 . [ Fork] [ ] and then [ clone] [ ] this repo .
33
- 2 . ** Change** to the repo directory.
32
+ 1 . [ Fork] [ ] and then [ clone] [ ] this repository .
33
+ 2 . ** Change** to the repository directory.
34
34
3 . ** Install or upgrade** to the [ ** active LTS** release] [ nodejs-rel ] of
35
35
** Node.js** . We recommend using ** [ nvm] [ ] ** to manage your Node
36
36
installation. Under Linux, run the following command (which will
@@ -104,7 +104,7 @@ The website is built from the following content:
104
104
105
105
# # Found a problem?
106
106
107
- If you find a problem with the content of this repo , or you would like to
107
+ If you find a problem with the content of this repository , or you would like to
108
108
request an enhancement, [create an issue][new-issue].
109
109
110
110
> ** NOTE** : As a general policy, we only _assign_ issues to community members
@@ -113,8 +113,8 @@ request an enhancement, [create an issue][new-issue].
113
113
# # Submitting a change
114
114
115
115
Enhancements and fixes to the website are most welcome! Before submitting a
116
- [pull request][pr] (PR) to the repo , run the following command and address any
117
- reported issues. Also commit any files changed by the ` fix` script:
116
+ [pull request][pr] (PR) to the repository , run the following command and address
117
+ any reported issues. Also commit any files changed by the ` fix` script:
118
118
119
119
` ` ` sh
120
120
npm run test-and-fix
@@ -133,12 +133,12 @@ To list available NPM scripts, run `npm run`.
133
133
134
134
If you change any content inside of a [content-modules][] submodule, then you' ll
135
135
need to **_first_** submit a PR (containing the submodule changes) to the
136
- submodule' s repo . Only after the submodule PR has been accepted, can you update
137
- the submodule and have the changes appear in this website.
136
+ submodule' s repository . Only after the submodule PR has been accepted, can you
137
+ update the submodule and have the changes appear in this website.
138
138
139
- It is easiest to manage your ` content-modules` changes by working with the repo
140
- that the corresponding submodule is linked to, rather than inside the submodule
141
- itself.
139
+ It is easiest to manage your ` content-modules` changes by working with the
140
+ repository that the corresponding submodule is linked to, rather than inside the
141
+ submodule itself.
142
142
143
143
> ** For expert contributors** , you can work directly in the submodule. You' ll
144
144
> then be able to directly build and serve your (submodule) changes. By default,
@@ -175,7 +175,7 @@ required.
175
175
[netlify]: https://netlify.com
176
176
[new-issue]:
177
177
https://github.com/open-telemetry/opentelemetry.io/issues/new/choose
178
- [nodejs-rel]: https://nodejs.org/en/about/releases/
178
+ [nodejs-rel]: https://nodejs.org/en/about/previous- releases
179
179
[nodejs-win]:
180
180
https://docs.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-windows
181
181
[nvm]:
0 commit comments