fix: remove broken tags (#977)

pages/en/lb4/Cassandra-connector.md

@@ -4,7 +4,6 @@ lang: en
 layout: readme
 source: loopback-connector-cassandra
 keywords: LoopBack, connector
-tags: readme
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Cassandra-connector.html
 summary: The Cassandra connector enables LoopBack applications to connect to Cassandra data sources.

pages/en/lb4/Cloudant-connector.md

@@ -4,11 +4,12 @@ lang: en
 layout: readme
 source: loopback-connector-cloudant
 keywords: LoopBack, connector
-tags: [connectors, readme]
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Cloudant-connector.html
 summary: The Cloudant connector enables LoopBack applications to connect to Cloudant data sources.
 ---
+
 {% include see-also.html content="
+
 - [Getting Started with LoopBack and IBM Cloudant](https://developer.ibm.com/bluemix/2015/09/10/getting-started-node-js-loopback-framework-ibm-cloudant/)
-" %} 
+  " %}

pages/en/lb4/Community-connectors.md

@@ -3,7 +3,6 @@ title: "Community connectors"
 lang: en
 layout: page
 keywords: LoopBack
-tags:
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Community-connectors.html
 summary:

pages/en/lb4/Connecting-to-Microsoft-SQL-Server.md

@@ -4,9 +4,8 @@ lang: en
 layout: readme
 source: loopback-example-database
 branch: mssql
-keywords: LoopBack
-tags: example_app
+keywords: LoopBack, example_app
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Connecting-to-Microsoft-SQL-Server.html
-summary: A brief tutorial on using the LoopBack MS SQL connector.  
+summary: A brief tutorial on using the LoopBack MS SQL connector.
 ---

pages/en/lb4/Connecting-to-MongoDB.md

@@ -3,8 +3,7 @@ title: "MongoDB Connector Tutorial"
 lang: en
 layout: readme
 source: loopback-example-database
-keywords: LoopBack
-tags: example_app
+keywords: LoopBack, example_app
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Connecting-to-MongoDB.html
 summary: A brief tutorial on using the LoopBack MongoDB connector.

pages/en/lb4/Connecting-to-MySQL.md

@@ -4,9 +4,8 @@ lang: en
 layout: readme
 source: loopback-example-database
 branch: mysql
-keywords: LoopBack
-tags: example_app
+keywords: LoopBack, example_app
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Connecting-to-MySQL.html
-summary: A brief tutorial on using the LoopBack MySQL connector.  
+summary: A brief tutorial on using the LoopBack MySQL connector.
 ---

pages/en/lb4/Connecting-to-Oracle.md

@@ -5,8 +5,7 @@ layout: navgroup
 navgroup: oracle
 source: loopback-example-database
 branch: oracle
-keywords: LoopBack
-tags: example_app
+keywords: LoopBack, example_app
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Connecting-to-Oracle.html
 summary: A brief tutorial on using the LoopBack Oracle connector.

pages/en/lb4/Connecting-to-PostgreSQL.md

@@ -4,9 +4,8 @@ lang: en
 layout: readme
 source: loopback-example-database
 branch: postgresql
-keywords: LoopBack
-tags: example_app
+keywords: LoopBack, example_app
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Connecting-to-PostgreSQL.html
-summary: A brief tutorial on using the LoopBack PostgreSQL connector.  
+summary: A brief tutorial on using the LoopBack PostgreSQL connector.
 ---

pages/en/lb4/Connecting-to-SOAP.md

@@ -3,11 +3,11 @@ title: "Connecting to SOAP web services"
 toc: false
 layout: page
 keywords: LoopBack
-tags:
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Connecting-to-SOAP.html
 summary: The LoopBack CLI enables you to easily create models based on a SOAP web service.
 ---
+
 {% include navgroups/soap.md %}
 {% include toc.html %}
 
@@ -23,7 +23,7 @@ XML document that describes web service endpoints, bindings, operations and sche
 
 Web services are still important in many enterprises, and the way to access them is via SOAP.
 SOAP is fairly heavy-weight, and working with XML-based SOAP
-payloads in Node.js is not easy.  It’s much easier to use JSON and to wrap or mediate a SOAP
+payloads in Node.js is not easy. It’s much easier to use JSON and to wrap or mediate a SOAP
 service and expose it as a REST API.
 
 To support the "API design first" approach, the [SOAP generator](SOAP-generator.html) creates LoopBack models and REST APIs for WSDL/SOAP operations to enable a LoopBack app to invoke a web service without the need to write code.
@@ -67,7 +67,7 @@ When prompted, respond as follows:
 - Enter http://www.webservicex.net/periodictable.asmx?WSDL for "HTTP URL or local fie system path to WSDL file" prompt.
 - Enter "y" to Expose operations as REST APIs.
 - Leave blank to "Maps WSDL binding operations to Node.js methods".
-- Select "y" to "Install "loopback-connector-soap" prompt.  This runs `npm install -s loopback-connector-soap`.
+- Select "y" to "Install "loopback-connector-soap" prompt. This runs `npm install -s loopback-connector-soap`.
 
 For more information on SOAP datasource properties, see [SOAP data source properties](http://loopback.io/doc/en/lb3/SOAP-connector.html).
 
@@ -103,7 +103,7 @@ Select the `periodictableSoap` binding.
 ? Select the binding: periodictableSoap
 ```
 
-After you choose a binding, the tool discovers and lists SOAP operations that the selected binding defines.  Press the space bar to select all of the listed SOAP operations.
+After you choose a binding, the tool discovers and lists SOAP operations that the selected binding defines. Press the space bar to select all of the listed SOAP operations.
 
 ```
 ◉ GetAtoms
@@ -138,6 +138,7 @@ The tool generates the following model definition files in the `server/models` d
 ### Run the application
 
 To run the application:
+
 ```sh
 node .
 ```

pages/en/lb4/Connectors-reference.md

@@ -3,7 +3,6 @@ title: "LoopBack data source connectors"
 lang: en
 toc: false
 keywords: LoopBack
-tags: [data_sources]
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Connectors-reference.html
 summary: LoopBack connectors implement the data exchange logic to communicate with backend systems such as relational or NoSQL databases, or other REST, or SOAP API.

pages/en/lb4/DB2-connector.md

@@ -3,9 +3,8 @@ title: "IBM Db2 connector"
 lang: en
 layout: readme
 source: loopback-connector-db2
-keywords: LoopBack
-tags: [connectors, readme]
+keywords: LoopBack, connector
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/DB2-connector.html
-summary: The Db2 connector enables LoopBack applications to connect to Db2 data sources. 
+summary: The Db2 connector enables LoopBack applications to connect to Db2 data sources.
 ---

pages/en/lb4/DB2-for-i-connector.md

@@ -3,8 +3,7 @@ title: "IBM Db2 for i connector"
 lang: en
 layout: readme
 source: loopback-connector-ibmi
-keywords: LoopBack
-tags: [connectors, readme]
+keywords: LoopBack, connector
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/DB2-for-i-connector.html
 summary: The loopback-connector-ibmi connector enables LoopBack applications to connect to IBM® Db2® for i data sources.

pages/en/lb4/DB2-for-z-OS-connector.md

@@ -3,8 +3,7 @@ title: "IBM Db2 for z/OS connector"
 lang: en
 layout: readme
 source: loopback-connector-db2z
-keywords: LoopBack
-tags: [connectors, readme]
+keywords: LoopBack, connector
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/DB2-for-z-OS-connector.html
 summary: The loopback-connector-db2z connector enables LoopBack applications to connect to IBM® Db2® for z/OS® data sources.

pages/en/lb4/DashDB.md

@@ -4,7 +4,6 @@ lang: en
 layout: readme
 source: loopback-connector-dashdb
 keywords: LoopBack, connector
-tags: [connectors, readme]
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/DashDB.html
 summary: The DashDB connector enables LoopBack applications to connect to DashDB data sources.

pages/en/lb4/Database-connectors.md

@@ -2,7 +2,6 @@
 title: "Database connectors"
 lang: en
 keywords: LoopBack
-tags: [data_sources]
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Database-connectors.html
 summary: LoopBack provides connectors for popular relational and NoSQL databases.

pages/en/lb4/Email-connector.md

@@ -2,8 +2,7 @@
 title: "Email connector"
 lang: en
 layout: page
-keywords: LoopBack
-tags: connectors
+keywords: LoopBack, connector
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Email-connector.html
 summary: The built-in email connectors enables applications to send email.
@@ -32,6 +31,7 @@ $ apic create --type datasource
 When prompted, select **Email** as the connector. This creates an entry in `datasources.json` like this (for example):
 
 {% include code-caption.html content="server/datasources.json" %}
+
 ```javascript
 ...
 "myEmailDataSource": {
@@ -46,6 +46,7 @@ When prompted, select **Email** as the connector. This creates an entry in `data
 Configure the email data source by editing `/server/datasources.json` (for example):
 
 {% include code-caption.html content="server/datasources.json" %}
+
 ```javascript
 {
   ...
@@ -81,11 +82,12 @@ See:
 
 - [Nodemailer: Using GMail](https://github.com/andris9/Nodemailer#using-gmail)
 - [Nodemailer: Authentication](https://github.com/andris9/nodemailer-smtp-transport#authentication) for more information.
-" %}
+  " %}
 
 For GMail, configure your email data source as follows:
 
 {% include code-caption.html content="server/datasources.json" %}
+
 ```javascript
 ...
 "Email": {
@@ -110,6 +112,7 @@ For GMail, configure your email data source as follows:
 Then, connect models to the data source in `/server/model-config.json` as follows (for example):
 
 {% include code-caption.html content="server/model-config.json" %}
+
 ```javascript
 {
   ...
@@ -125,25 +128,29 @@ Then, connect models to the data source in `/server/model-config.json` as follow
 The following example illustrates how to send emails from an app. Add the following code to a file in the `/models` directory:
 
 {% include code-caption.html content="server/models/model.js" %}
+
 ```javascript
-module.exports = function(MyModel) {
+module.exports = function (MyModel) {
   // send an email
-  MyModel.sendEmail = function(cb) {
-    MyModel.app.models.Email.send({
-      to: 'foo@bar.com',
-      from: 'you@gmail.com',
-      subject: 'my subject',
-      text: 'my text',
-      html: 'my <em>html</em>'
-    }, function(err, mail) {
-      console.log('email sent!');
-      cb(err);
-    });
-  }
+  MyModel.sendEmail = function (cb) {
+    MyModel.app.models.Email.send(
+      {
+        to: "foo@bar.com",
+        from: "you@gmail.com",
+        subject: "my subject",
+        text: "my text",
+        html: "my <em>html</em>",
+      },
+      function (err, mail) {
+        console.log("email sent!");
+        cb(err);
+      }
+    );
+  };
 };
 ```
 
-The default model definition file is [common/models/email.json](https://github.com/strongloop/loopback/blob/master/common/models/email.json) in the LoopBack repository. 
+The default model definition file is [common/models/email.json](https://github.com/strongloop/loopback/blob/master/common/models/email.json) in the LoopBack repository.
 
 ## Confirming email address
 

pages/en/lb4/Example-kv-connector.md

@@ -3,8 +3,7 @@ title: "KV connector example"
 lang: en
 layout: readme
 source: loopback-example-kv-connectors
-keywords: LoopBack
-tags: example_app
+keywords: LoopBack, example_app
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Example-kv-connector.html
 summary: A simple example of using the LoopBack KV connectors.

pages/en/lb4/Informix.md

@@ -4,7 +4,6 @@ lang: en
 layout: readme
 source: loopback-connector-informix
 keywords: LoopBack, connector
-tags: [connectors, readme]
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Informix.html
 summary: The Informix connector enables LoopBack applications to connect to Informix data sources.

pages/en/lb4/Installing-the-Oracle-connector.md

@@ -5,13 +5,13 @@ layout: navgroup
 navgroup: oracle
 source: loopback-oracle-installer
 keywords: LoopBack
-tags:
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Installing-the-Oracle-connector.html
 summary: The loopback-oracle-installer module takes care of binary dependencies and simplifies the process of installing the Oracle connector.
 ---
+
 {% include tip.html content="
 Use the [Oracle installer command](Oracle-installer-command.html), `lb oracle`,
 to easily install and troubleshoot installing `loopback-oracle-installer`
-and the Oracle data source connector.  
+and the Oracle data source connector.
 " %}

pages/en/lb4/JSON-RPC-connector.md

@@ -4,8 +4,7 @@ lang: en
 layout: readme
 source: loopback-connector-jsonrpc
 keywords: LoopBack, connector
-tags: [connectors, readme]
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/JSON-RPC-connector.html
-summary:  The LoopBack JSON-RPC Connector enables LoopBack applications to call JSON-RPC services. 
+summary: The LoopBack JSON-RPC Connector enables LoopBack applications to call JSON-RPC services.
 ---

pages/en/lb4/MQLight-connector.md

@@ -4,7 +4,6 @@ lang: en
 layout: readme
 source: loopback-connector-mqlight
 keywords: LoopBack, connector
-tags: [connectors, readme]
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/MQLight-connector.html
 summary: The MQ Light connector enables LoopBack applications to use the MQ Light messaging API.

pages/en/lb4/Memory-connector.md

@@ -2,8 +2,7 @@
 title: "Memory connector"
 lang: en
 layout: page
-keywords: LoopBack
-tags: connectors
+keywords: LoopBack, connector
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/Memory-connector.html
 summary: The built-in memory connector is a persistent data source for development and testing.
@@ -16,12 +15,12 @@ Although the memory connector is very well tested it is not suitable for product
 
 The memory connector supports:
 
-* Standard query and create, read, update, and delete operations, so you can test models against an in-memory data source.
-* Geo-filtering when using the `find()` operation with an attached model.
+- Standard query and create, read, update, and delete operations, so you can test models against an in-memory data source.
+- Geo-filtering when using the `find()` operation with an attached model.
   See [GeoPoint class](http://apidocs.loopback.io/loopback-datasource-juggler/#geopoint) for more information on geo-filtering.
 
 {% include important.html content="
-The memory connector is designed for development and testing of a single-process application without setting up a database.  It cannot be used in a cluster as the worker processes will have their own isolated data not shared in the cluster.
+The memory connector is designed for development and testing of a single-process application without setting up a database. It cannot be used in a cluster as the worker processes will have their own isolated data not shared in the cluster.
 
 You can persist data between application restarts using the `file` property. See [Data persistence](#data-persistence) for more information.
 " %}
@@ -31,6 +30,7 @@ You can persist data between application restarts using the `file` property. See
 By default, an application created with the [Application generator](Application-generator.html) has a memory data source defined; for example:
 
 {% include code-caption.html content="/server/datasources.json" %}
+
 ```javascript
 "db": {
     "name": "db",
@@ -83,6 +83,7 @@ To maintain data across application restarts, specify a JSON file in which to st
 The simplest way to do this is by editing `server/datasources.json`; for example:
 
 {% include code-caption.html content="server/datasources.json" %}
+
 ```javascript
 {
   "db": {
@@ -96,10 +97,11 @@ The simplest way to do this is by editing `server/datasources.json`; for example
 You can also set the persistence file in a boot script; for example:
 
 {% include code-caption.html content="server/boot/script.js" %}
+
 ```javascript
 var memory = loopback.createDataSource({
   connector: loopback.Memory,
-  file: "mydata.json"
+  file: "mydata.json",
 });
 ```
 

pages/en/lb4/MongoDB-connector.md

@@ -4,7 +4,6 @@ lang: en
 layout: readme
 source: loopback-connector-mongodb
 keywords: LoopBack, connector
-tags: readme
 sidebar: lb4_sidebar
 permalink: /doc/en/lb4/MongoDB-connector.html
 summary: The MongoDB connector enables LoopBack applications to connect to MongoDB data sources.