Updates

Author: gabydreckschmidt

faqs-general.md

@@ -91,6 +91,8 @@ The Lite plan provides 50 node-hours of free {{site.data.keyword.iae_full_notm}}
 
 A cluster created using a Lite plan has 1 master and 1 data node (2 nodes in total) and will run for 25 hours on the clock (50 hours/2 nodes). The node-hours cannot be paused, for example, you cannot use 10 node-hours, pause, and then come back and use the remaining 40 node-hours.
 
+Remember that you must sign up with IBM to try out the Lite plan.  
+
 ## What types of service maintenance exist in {{site.data.keyword.iae_full_notm}}?
 {: #service-maintenance}
 {: faq}

images/generate-password-in-console.png

@@ -35,7 +35,7 @@ You can deploy {{site.data.keyword.iae_full_notm}} service instances in the foll
 
 ## Cluster architecture
 
-A cluster consists of a management instance and one or more compute instances. The management instance itself consists of three management nodes, which run in the management instance. Each of the compute nodes runs in a separate compute instance.
+A cluster consists of a management instance and one or more compute instances. The management instance consists of three management nodes that run in the instance. Each compute node runs in a separate compute instance.
 
 Note: You are billed only at the instance level. For more details on billing, see [{{site.data.keyword.iae_full_notm}}   Pricing](https://www.ibm.com/cloud/analytics-engine/pricing){: external}.
 
@@ -49,7 +49,7 @@ Ambari and all of the Hadoop and Spark components of the cluster run on the mana
 
 ### Compute nodes
 
-Compute nodes are where the execution of jobs happens. You define the number of compute nodes at the time of cluster creation. Each of the compute nodes is designated as `dn001`, `dn002` and so on.
+Compute nodes are where the execution of jobs happens. You define the number of compute nodes at the time the cluster is created. Each of the compute nodes is designated as `dn001`, `dn002` and so on.
 
 ### Summary of cluster nodes
 
@@ -67,14 +67,14 @@ Cluster services are made available through various endpoints as described in th
 
 From the endpoint list, you can see that the following ports are open for inbound traffic:
 
--	**9443**: this is the Admin port.
+-	**9443**: This is the Admin port.
 
- The Ambari UI console and APIs are exposed at port 9443 (`https://xxxxx-mn001.<region>.ae.appdomain.cloud:9443`).
+ The Ambari UI console and APIs are exposed on port 9443 (`https://xxxxx-mn001.<region>.ae.appdomain.cloud:9443`).
 -	**8443**: cluster services like Hive, Spark, Livy, Phoenix, and so on are made available for programmatic consumption through the Knox gateway on port 8443
 
--	**22**: the cluster itself is accessible via SSH at standard port 22.
+-	**22**: The cluster itself is accessible via SSH through the  standard port 22.
 
- When you SSH to a cluster (as described [here](/docs/AnalyticsEngine?topic=AnalyticsEngine-connect-SSH)) you essentially log in to `mn003`. Once you have logged in to `mn003`, you can SSH to the compute nodes (referred to as `dn001`, `dn002` etc) and to `mn002`.
+ When you SSH to a cluster (as described [here](/docs/AnalyticsEngine?topic=AnalyticsEngine-connect-SSH)) you essentially log in to `mn003`. Once you have logged in to `mn003`, you can SSH to the compute nodes (referred to as `dn001`, `dn002`, and so on) and to `mn002`.
 
 For example, to log in to a cluster in the US-South region, as given in the endpoint listing, enter:
 ```

index.md

@@ -1,8 +1,8 @@
 ---
 
 copyright:
-  years: 2017, 2019
-lastupdated: "2019-02-26"
+  years: 2017, 2020
+lastupdated: "2020-07-13"
 
 subcollection: AnalyticsEngine
 
@@ -17,8 +17,8 @@ After your {{site.data.keyword.iae_full_notm}} service instance was created, you
 
 - By invoking the {{site.data.keyword.iae_full_notm}} [`reset_password`](/docs/AnalyticsEngine?topic=AnalyticsEngine-reset-cluster-password#reset-cluster-password) REST API. Calling this API is the only way in which the cluster password is shown to you. You can also use the API to reset the password if you need to.
 
-- By resetting the cluster password on the {{site.data.keyword.iae_full_notm}} service instance page from the {{site.data.keyword.Bluemix_notm}} console.  
+- By generating the cluster password on the {{site.data.keyword.iae_full_notm}} service instance page from the {{site.data.keyword.Bluemix_notm}} console.  
 
-  ![Shows the various states during cluster  provisioning.](images/change-password-in-console.png)
+  ![Shows the various states during cluster  provisioning.](images/generate-password-in-console.png)
 
-**Important:** The method of getting the cluster credentials by creating service keys is being deprecated. The service credentials will no longer show the cluster credentials. The service credentials will only include the service endpoints and a role-linked API key for using the {{site.data.keyword.iae_full_notm}} REST API.  
+**Important:** The service credentials are not shown with the cluster credentials. The service credentials only include the service endpoints and a role-linked API key for using the {{site.data.keyword.iae_full_notm}} REST API.