diff --git a/README.md b/README.md index 2356485ca..0a9c410d8 100644 --- a/README.md +++ b/README.md @@ -72,7 +72,7 @@ summary: A brief tutorial on creating an Angular client app using the Loopback A ### Linting Readmes -There is an additional `npm script` that "lints" the readmes for markdown formatting problems. It is currently "experimental", see #49 for more info. +There is an additional `npm script` that "lints" the readmes for markdown formatting problems. It is currently "experimental", see [this issue](https://github.com/strongloop/loopback.io/issues/49#issuecomment-253672668) for more info. You can run this script thus: diff --git a/pages/en/contrib/LTS.md b/pages/en/contrib/LTS.md index fd81a77d3..08341b89b 100644 --- a/pages/en/contrib/LTS.md +++ b/pages/en/contrib/LTS.md @@ -12,7 +12,7 @@ In general, LoopBack version numbers adhere to [semantic versioning](http://semv The LoopBack project maintains: - A _Current_ version where most of the development occurs. -- A _Long-term suppoort (LTS)_ version that does not add new features but gets bug fixes. +- A _Long-term support (LTS)_ version that does not add new features but gets bug fixes. - One (or more) _maintenance_ versions that receive only critical bug fixes. ## LTS versions diff --git a/pages/en/lb3/Basic-model-object.md b/pages/en/lb3/Basic-model-object.md index bd5c01f4b..0a86ea108 100644 --- a/pages/en/lb3/Basic-model-object.md +++ b/pages/en/lb3/Basic-model-object.md @@ -4,8 +4,8 @@ lang: en layout: page keywords: LoopBack tags: -sidebar: lb2_sidebar -permalink: /doc/en/lb2/Basic-model-object.html +sidebar: lb3_sidebar +permalink: /doc/en/lb3/Basic-model-object.html summary: --- diff --git a/pages/en/lb3/LoopBack-core-concepts.md b/pages/en/lb3/LoopBack-core-concepts.md index ccc968bf7..1ce029dc9 100644 --- a/pages/en/lb3/LoopBack-core-concepts.md +++ b/pages/en/lb3/LoopBack-core-concepts.md @@ -24,7 +24,7 @@ LoopBack models are JavaScript objects with both Node and REST APIs. **A key powerful feature of LoopBack is that when you define a model it automatically comes with a predefined REST API with a full set of create, read, update, and delete operations.**   -The [Basic model object](Basic-model-object.html) has methods for adding [hooks](Model-hooks.html) and for [validating data](Validating-model-data.html). +The [Basic model object](Basic-model-object.html) has methods for adding [hooks](Operation-hooks.html) and for [validating data](Validating-model-data.html). Other model objects all "inherit from" it. Models have an inheritance hierarchy, as shown at right: When you attach a model to a persistent data source it becomes a [connected model](Connected-model-object.html) with create, retrieve, update, and delete operations. LoopBack's built-in models inherit from it. @@ -101,7 +101,6 @@ with a full set of create, read, update, and delete operations from the [Persi Update (Modify) - POST /modelName
PUT /modelName updateAll()* diff --git a/pages/en/lb3/Managing-users.md b/pages/en/lb3/Managing-users.md index 453885ac7..c72140a01 100644 --- a/pages/en/lb3/Managing-users.md +++ b/pages/en/lb3/Managing-users.md @@ -28,10 +28,6 @@ functionality that you can use via your custom model. In addition, LoopBack does not support multiple models based on the User model in a single application. That is, you cannot have more than one model derived from the built-in User model in a single app. " %} -Watch this video for an introduction to user management in LoopBack: - - - ## Creating and authenticating users The basic process to create and authenticate users is: @@ -150,7 +146,7 @@ See [Partitioning users with realms](Partitioning-users-with-realms.html). ## Security considerations -When a user's account is compromised (for example their password is leaked or the attacker gains +When a user's account is compromised (for example their password is leaked or the attacker gains access to their email account), the app needs to be able to prevent continued use of the hijacked account. To address this case, LoopBack invalidates access tokens (logs out sessions)