[deprecation-of-passwords] - Changes in the review

Author: GuiLeme

_data/create.yml

@@ -10,11 +10,11 @@
 
 - name: "attendeePW"
   type: "String"
-  description: "The password that the <a href=\"#join\">join</a> URL can later provide as its <code class=\"language-plaintext highlighter-rouge\">password</code> parameter to indicate the user will join as a viewer.  If no <code class=\"language-plaintext highlighter-rouge\">attendeePW</code> is provided, the <code class=\"language-plaintext highlighter-rouge\">create</code> call will return a randomly generated <code class=\"language-plaintext highlighter-rouge\">attendeePW</code> password for the meeting."
+  description: "<b>[DEPRECATED]</b> The password that the <a href=\"#join\">join</a> URL can later provide as its <code class=\"language-plaintext highlighter-rouge\">password</code> parameter to indicate the user will join as a viewer.  If no <code class=\"language-plaintext highlighter-rouge\">attendeePW</code> is provided, the <code class=\"language-plaintext highlighter-rouge\">create</code> call will return a randomly generated <code class=\"language-plaintext highlighter-rouge\">attendeePW</code> password for the meeting."
 
 - name: "moderatorPW"
   type: "String"
-  description: "The password that will <a href=\"#join\">join</a> URL can later provide as its <code class=\"language-plaintext highlighter-rouge\">password</code> parameter to indicate the user will as a moderator.  if no <code class=\"language-plaintext highlighter-rouge\">moderatorPW</code> is provided, <code class=\"language-plaintext highlighter-rouge\">create</code> will return a randomly generated <code class=\"language-plaintext highlighter-rouge\">moderatorPW</code> password for the meeting."
+  description: "<b>[DEPRECATED]</b> The password that will <a href=\"#join\">join</a> URL can later provide as its <code class=\"language-plaintext highlighter-rouge\">password</code> parameter to indicate the user will as a moderator.  if no <code class=\"language-plaintext highlighter-rouge\">moderatorPW</code> is provided, <code class=\"language-plaintext highlighter-rouge\">create</code> will return a randomly generated <code class=\"language-plaintext highlighter-rouge\">moderatorPW</code> password for the meeting."
 
 - name: "welcome"
   required: false

_data/end.yml

@@ -5,4 +5,4 @@
 - name: "password"
   required: true
   type: "String"
-  description: "The moderator password for this meeting. You can not end a meeting using the attendee password."
+  description: "<b>[DEPRECATED]</b> The moderator password for this meeting. You can not end a meeting using the attendee password."

_data/join.yml

@@ -11,7 +11,7 @@
 - name: "password"
   required: true
   type: "String"
-  description: "This password value is used to determine the role of the user based on whether it matches the moderator or attendee password.  Note: This parameter is <b>not</b> required when the role parameter is passed."
+  description: "<b>[DEPRECATED]</b> This password value is used to determine the role of the user based on whether it matches the moderator or attendee password.  Note: This parameter is <b>not</b> required when the role parameter is passed."
 
 - name: "role"
   required: true

_posts/2.4/2021-06-09-new.md

@@ -393,17 +393,17 @@ Even though it is still possible to create a meeting with a password, it is now
 - **Create** - It is possible and recommended to not use the passwords while creating the request:
 
 ```url 
-https://bbb25.bbbvm.imdt.com.br/bigbluebutton/api/create?allowStartStopRecording=true&attendeePW=ap&moderatorPW=mp&... &checksum=
+https://bbb.example.com/bigbluebutton/api/create?allowStartStopRecording=true&attendeePW=ap&moderatorPW=mp&... &checksum=
 ```
 or 
 ```url 
-https://bbb25.bbbvm.imdt.com.br/bigbluebutton/api/create?allowStartStopRecording=true&... &checksum=
+https://bbb.example.com/bigbluebutton/api/create?allowStartStopRecording=true&... &checksum=
 ```
 
-- **Join** - These requests don't need to follow the `/create` endpoint, on the grounds that it has its own parameter to know the role of the user. Se the explanation down below:
+- **Join** - These requests don't need to follow the `/create` endpoint, on the grounds that it has its own parameter to know the role of the user. See the explanation down below:
 
   - In any cases, if the `role` parameter is sent along, it will be respected, even if `password` is passed too;
-  - If the `role` parameter is not passed in the call, and the password exists (i.e., it has been sent in `/create` endpoint), then the password is mandatory for the `/join` endpoint to acknowledge which role does the user have.
+  - If the `role` parameter is not passed in the request, and the password exists (i.e., it has been sent in `/create` endpoint), then the password is mandatory for the `/join` endpoint to identify which role the user has.
   - If the password does not exist (i.e., it was not defined in `/create` endpoint), then the `role` parameter is mandatory, otherwise it is not possible to enter a meeting.
 
 - **End** - the password is really not used here. But, if it was set (in the `/create` endpoint) and passed along in the `end` endpoint, it will be validated, otherwise, it won't.