Skip to content

Commit a512447

Browse files
committed
update some docs, typos, etc..
1 parent 667f0fa commit a512447

2 files changed

Lines changed: 27 additions & 15 deletions

File tree

jooby-quartz/src/main/java/org/jooby/quartz/Quartz.java

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@
5050
/**
5151
* Build and create a {@link Scheduler Quartz Scheduler} and {@link Job jobs}.
5252
*
53-
* <h1>Getting Started</h1>
53+
* <h1>usage</h1>
5454
*
5555
* <pre>
5656
* {
@@ -60,7 +60,7 @@
6060
*
6161
* Previous example will startup Quartz and schedule MyJob.
6262
*
63-
* <h1>Jobs</h1>
63+
* <h1>jobs</h1>
6464
* <p>
6565
* A job can implement the {@link Job} interface as described in the <a
6666
* href="http://quartz-scheduler.org/documentation">Quartz documentation</a>
@@ -75,7 +75,7 @@
7575
* package name of the job class.
7676
* </p>
7777
*
78-
* <h2>Job methods</h2>
78+
* <h2>job methods</h2>
7979
* <p>
8080
* A job method must follow this rules:
8181
* </p>
@@ -89,9 +89,9 @@
8989
*
9090
* The next section will you show how to add a trigger to a job and some examples too.
9191
*
92-
* <h1>Triggers</h1>
92+
* <h1>triggers</h1>
9393
* <p>
94-
* Trigger are defined by the {@link Scheduled} annotation. The annotation defined a single and
94+
* Trigger are defined by the {@link Scheduled} annotation. The annotation defines a single and
9595
* required attributes, which is basically a trigger expression or a reference to it.
9696
* </p>
9797
*
@@ -143,7 +143,7 @@
143143
* expressions.
144144
* </p>
145145
*
146-
* <h1>Grouping jobs together</h1>
146+
* <h1>grouping jobs together</h1>
147147
* <p>
148148
* If you have two or more jobs doing something similar, it is possible to group all them into one
149149
* single class:
@@ -163,7 +163,7 @@
163163
* }
164164
* </pre>
165165
*
166-
* <h1>Dependency Injection</h1>
166+
* <h1>dependency injection</h1>
167167
* <p>
168168
* Not much to add here, just let you know jobs are created by Guice.
169169
* </p>
@@ -201,7 +201,7 @@
201201
* }
202202
* </pre>
203203
*
204-
* <h1>Configuration</h1>
204+
* <h1>configuration</h1>
205205
* <p>
206206
* Example: Setting max number of threads
207207
* </p>
@@ -216,7 +216,7 @@
216216
* <code>*.conf</code> file, NOT in a custom <code>quartz.properties</code> file.
217217
* </p>
218218
*
219-
* <h2>Jdbc Store</h2>
219+
* <h2>jdbc store</h2>
220220
* <p>
221221
* Jdbc Store is fully supported but it depends on the <code>jooby-jdbc</code> module. So, in order
222222
* to use the Jdbc Store you need to follow these steps:
@@ -243,9 +243,11 @@
243243
* org.quartz.jobStore.dataSource = db
244244
* </pre>
245245
*
246-
* <h1>Adding jobs programmatically</h1> When {@link Scheduled} isn't not enough and/or if you
247-
* prefer to build jobs manually, you can try
246+
* <h1>adding jobs programmatically</h1>
247+
* <p>
248+
* When {@link Scheduled} isn't not enough and/or if you prefer to build jobs manually, you can try
248249
* one of the available alternatives.
250+
* </p>
249251
*
250252
* <p>
251253
* Example 1: build the trigger and use default job naming

md/processor.js

Lines changed: 14 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -212,22 +212,32 @@ vars.push({
212212

213213
vars.push({
214214
name: 'jooby',
215-
data: '[Jooby](http://jooby.org/)'
215+
data: '[Jooby](http://jooby.org)'
216216
});
217217

218218
vars.push({
219219
name: 'netty',
220-
data: '[Netty](http://netty.io/)'
220+
data: '[Netty](http://netty.io)'
221221
});
222222

223223
vars.push({
224224
name: 'npm',
225-
data: '[npm](https://www.npmjs.com/)'
225+
data: '[npm](https://www.npmjs.com)'
226226
});
227227

228228
vars.push({
229229
name: 'grunt',
230-
data: '[npm](http://gruntjs.com/)'
230+
data: '[npm](http://gruntjs.com)'
231+
});
232+
233+
vars.push({
234+
name: 'redis',
235+
data: '[Redis](http://redis.io)'
236+
});
237+
238+
vars.push({
239+
name: 'jedis',
240+
data: '[Jedis](https://github.com/xetorthio/jedis)'
231241
});
232242

233243
/**

0 commit comments

Comments
 (0)