Create an informative issue (See each section, incomplete templates/issues won't be triaged)

Using the current documentation as a model, please complete the issue template. 

Note: Doc team updates the current version and the two previous versions (n-2). For earlier versions, we will address only high-priority, customer-reported issues for releases in support.

Prerequisite: Start with what we have

Always look at the current documentation to describe the change that is needed. Use the source or portal link for Step 4:

 - Use the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes

 - Use the GitHub link to find the staged docs in the repository: https://github.com/stolostron/rhacm-docs 

Describe the changes in the doc and link to your dev story

Provide info for the following steps:

1. - [x] Mandatory Add the required version to the Fix version/s field.

2. - [x] Mandatory Choose the type of documentation change.

      - [ ] New topic in an existing section or new section
      - [x] Update to an existing topic

3. - [x] Mandatory for GA content:
            
       - [x] Add steps and/or other important conceptual information here:
Couldn't find where to place this data in this template, so I'll put it here:
The operation of Enabling node auto-scaling for hosted cluster is well defined here: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.8/html/clusters/cluster_mce_overview#enable-node-auto-scaling-hosted-cluster

However Disabling node auto-scaleing is not defined, is should, and needs to be documented as well.

I've verified that this worked for going from "not autoscaling mode" to "manually scaled mode":
oc -n ${CLUSTERS_NAMESPACE} patch nodepool ${HOSTED_CLUSTER_NAME} --type=json -p '[

,

]'
 

It raises the following questions:

• Is that the way to go for disabling autoscale?
• Can we also just remove the /spec/autoScaling for disabling, without setting a "/spec/replicas"?
• If yes, what will be the number of nodes after disabling, as it was before (not scaled), as it is now (/status/replicas),or maybe something else?
• Enabling auto-scaling moves us from "scaled" or "not-scaled" mode to "auto-scaling" mode, will disabling allow us to chose to be back in "scaled"(as in the example I've verified) or "not-scaled"(as was before) ?
         
              
         - [x] Add Required access level for the user to complete the task here: admin
         

       - [ ] Add verification at the end of the task, how does the user verify success (a command to run or a result to see?)
     
     
       - [x] Add link to dev story here: as in the original ticket : https://issues.redhat.com/browse/ACM-5637

4. - [ ] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation: