Skip to content

Commit ffdc62d

Browse files
committed
Fix incorrect usage examples
1 parent 0a776fa commit ffdc62d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ This can be useful if you'd like to reuse strategy objects but under a different
7878
Most passport strategies that use OAuth 2.0 should work without any additional configuration. Some strategies, however require custom OAuth configuration, or do not expose an oauth2 adapter for internal use. In these cases, a callback can be specified by calling the `use` function with an extra `options` parameter:
7979

8080
```js
81-
passport.use(strategy, {
81+
refresh.use(strategy, {
8282
setRefreshOAuth2() {
8383
return new OAuth2(/* custom oauth config */);
8484
},
@@ -90,7 +90,7 @@ The `setRefreshOAuth2` callback should return an instance of [the node-oauth OAu
9090
The callback is called with two named parameters, which can be used to further customise the OAuth2 adapter:
9191

9292
```js
93-
passport.use(strategy, {
93+
refresh.use(strategy, {
9494
setRefreshOAuth2({ strategyOAuth2, refreshOAuth2 }) {
9595
// These named parameters are set for most strategies.
9696
// The `refreshOAuth2` instance is a clone of the one supplied by the strategy, inheriting most of its config.

0 commit comments

Comments
 (0)