Skip to content

Commit

Permalink
spelling: propagate
Browse files Browse the repository at this point in the history
  • Loading branch information
jsoref authored and bitwiseman committed Apr 20, 2020
1 parent fd350bf commit 5c37ebd
Show file tree
Hide file tree
Showing 4 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ All commits should be squashed before being merged to `master` to preserve a san

For Jenkins-ish code on the server side (which Blue Ocean is built on) - follow the same as: https://wiki.jenkins-ci.org/display/JENKINS/Beginners+Guide+to+Contributing#BeginnersGuidetoContributing-HowaboutJavacode%3F - you can make this a bit easier by importing the .editorconfig file into your favourite editor so it autoformats for you.

## Javascript and web
## JavaScript and web

(this is a bit vague while sorted out. Any help/automation appreciated)

Expand Down
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ Then open http://localhost:8080/jenkins/blue to start using Blue Ocean.

The Jenkins Classic UI exists side-by-side at its usual place at http://localhost:8080/jenkins.

NOTE: while running in this mode, Jenkins will automatically re-compile your Javascript files
NOTE: while running in this mode, Jenkins will automatically re-compile your JavaScript files
and LESS files for all local plugins (including those linked with `hpi:hpl`) where a `package.json` is found
that contains a `mvnbuild` script. If you would like to disable this behavior, you may set
the system property: `-Dblueocean.features.BUNDLE_WATCH_SKIP=true`
Expand Down Expand Up @@ -116,7 +116,7 @@ Look in following README's for:

### Building plugins for Blue Ocean

Blue Ocean plugins use the same plugin mechanism as Jenkins for distribution and installation, but involve a lot more Javascript if they have GUI elements.
Blue Ocean plugins use the same plugin mechanism as Jenkins for distribution and installation, but involve a lot more JavaScript if they have GUI elements.

The best way to get started is to look at the tutorial and Yeoman starter project here:
https://www.npmjs.com/package/generator-blueocean-usain
Expand All @@ -135,7 +135,7 @@ Blue Ocean has javascript extension points that currently work with react compon

As npm packages are used node-gyp may be involved and this can require some tools installed to build native dependencies (native components are not used at runtime) - see https://www.npmjs.com/package/node-gyp for instructions for your platform

If you are working on the Javascript, you will need node installed, look at the version in the pom.xml for the minimum version required.
If you are working on the JavaScript, you will need node installed, look at the version in the pom.xml for the minimum version required.

__NOTE__: look in the README.md of the respective modules for more detailed dev docs.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -211,7 +211,7 @@ public void tinySleep(long timeToSleep) {
}

/**
* Wait until the SSE is fully connected so events will propegate properly
* Wait until the SSE is fully connected so events will propagate properly
*/
public void untilSSEReady() {
// make sure the variable is defined
Expand Down
2 changes: 1 addition & 1 deletion blueocean-web/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ In general, you shouldn't need to modify stuff in for plugins or features as it

Look for blueocean.js for excitement.

## how this works with Javascript
## how this works with JavaScript

All runtime JavaScript artifacts are generated during the build and added to the plugin HPI.

Expand Down

0 comments on commit 5c37ebd

Please sign in to comment.