docs: rename managed to cloud (#6689)

### Describe Your Changes

These changes were made as part of the title transition from Managed
VictoriaMetrics to VictoriaMetrics Cloud

### Checklist

The following checks are **mandatory**:

- [x] My change adheres [VictoriaMetrics contributing
guidelines](https://docs.victoriametrics.com/contributing/).

docs/FAQ.md

@@ -215,11 +215,10 @@ We provide commercial support for both versions. [Contact us](mailto:info@victor
 
 The following commercial versions of VictoriaMetrics are available:
 
-* [Managed VictoriaMetrics at AWS](https://aws.amazon.com/marketplace/pp/prodview-4tbfq5icmbmyc) (aka managed Prometheus).
+* [VictoriaMetrics Cloud](https://cloud.victoriametrics.com/signUp?utm_source=website&utm_campaign=docs_vm_faq) – the most cost-efficient hosted monitoring platform, operated by VictoriaMetrics core team.
 
 The following commercial versions of VictoriaMetrics are planned:
 
-* Managed VictoriaMetrics at Google Cloud.
 * Cloud monitoring solution based on VictoriaMetrics.
 
 [Contact us](mailto:info@victoriametrics.com) for more information on our plans.

docs/Quick-Start.md

@@ -20,7 +20,7 @@ VictoriaMetrics is distributed in two forms:
 
 Single-server-VictoriaMetrics VictoriaMetrics is available as:
 
-* [Managed VictoriaMetrics at AWS](https://aws.amazon.com/marketplace/pp/prodview-4tbfq5icmbmyc)
+* [VictoriaMetrics Cloud](https://cloud.victoriametrics.com/signUp?utm_source=website&utm_campaign=docs_vm_quickstart) – the most cost-efficient hosted monitoring platfor, operated by VictoriaMetrics core team.
 * [Docker images](https://hub.docker.com/r/victoriametrics/victoria-metrics/)
 * [Helm Charts](https://github.com/VictoriaMetrics/helm-charts#list-of-charts)
 * [Binary releases](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/latest)

docs/data-ingestion/Proxmox.md

@@ -16,7 +16,7 @@ Since Proxmox Virtual Environment(PVE) and Proxmox Backup Server(PBS) support se
 Currently PVE and PBS only support using an Authorization Token for authentication and does not support basic auth or a username and password.
 
 ## Proxmox Virtual Environment (PVE)
-If want help Sending your data to Managed VictoriaMetrics check out [our blog](https://victoriametrics.com/blog/proxmox-monitoring-with-dbaas/).
+If want help Sending your data to VictoriaMetrics Cloud check out [our blog](https://victoriametrics.com/blog/proxmox-monitoring-with-dbaas/).
 
 1. Login to PVE as an administrator
 2. Go to DataCenter > MetricServer > Add > InfluxDB
@@ -65,4 +65,4 @@ You should see 1 time series per node in your PVE cluster.
 
 
 # References
-- [Blog Post for configuring Managed VictoriaMetrics and Proxmox VE](https://victoriametrics.com/blog/proxmox-monitoring-with-dbaas/)
+- [Blog Post for configuring VictoriaMetrics Cloud and Proxmox VE](https://victoriametrics.com/blog/proxmox-monitoring-with-dbaas/)

docs/enterprise.md

@@ -28,7 +28,7 @@ The use of VictoriaMetrics Enterprise components is permitted in the following c
 - Production use if you have a valid enterprise contract or valid permit from VictoriaMetrics company.
   Please contact us via [this page](https://victoriametrics.com/products/enterprise/) if you are intereseted in such a contract.
 
-- [Managed VictoriaMetrics](https://docs.victoriametrics.com/managed-victoriametrics/) is built on top of VictoriaMetrics Enterprise.
+- [VictoriaMetrics Cloud](https://docs.victoriametrics.com/victoriametrics-cloud/) is built on top of VictoriaMetrics Enterprise.
 
 See [these docs](#running-victoriametrics-enterprise) for details on how to run VictoriaMetrics enterprise.
 

docs/guides/README.md

@@ -6,6 +6,6 @@
 1. [Migrate from InfluxDB to VictoriaMetrics](migrate-from-influx.html)
 1. [Multi-regional setup with VictoriaMetrics: Dedicated regions for monitoring](multi-regional-setup-dedicated-regions.html)
 1. [How to delete or replace metrics in VictoriaMetrics](guide-delete-or-replace-metrics.html)
-1. [How to monitor kubernetes cluster using Managed VictoriaMetrics](/managed-victoriametrics/how-to-monitor-k8s.html)
+1. [How to monitor kubernetes cluster using VictoriaMetrics Cloud](/victoriametrics-cloud/how-to-monitor-k8s.html)
 1. [How to configure vmgateway for multi-tenant access using Grafana and OpenID Connect](grafana-vmgateway-openid-configuration.html)
 1. [How to setup vmanomaly together with vmalert](/anomaly-detection/guides/guide-vmanomaly-vmalert/README.md)

docs/guides/understand-your-setup-size.md

@@ -8,7 +8,7 @@ menu:
 aliases:
 - /guides/understand-your-setup-size.html
 ---
-The docs provide a simple and high-level overview of Ingestion Rate, Active Time Series, and Query per Second. These terms are a part of capacity planning ([Single-Node](https://docs.victoriametrics.com/single-server-victoriametrics/#capacity-planning), [Cluster](https://docs.victoriametrics.com/cluster-victoriametrics/#capacity-planning)) and [Managed VictoriaMetrics](https://docs.victoriametrics.com/managed-victoriametrics/) pricing.
+The docs provide a simple and high-level overview of Ingestion Rate, Active Time Series, and Query per Second. These terms are a part of capacity planning ([Single-Node](https://docs.victoriametrics.com/single-server-victoriametrics/#capacity-planning), [Cluster](https://docs.victoriametrics.com/cluster-victoriametrics/#capacity-planning)) and [VictoriaMetrics Cloud](https://docs.victoriametrics.com/victoriametrics-cloud/) pricing.
 
 ## Terminology
 
@@ -101,12 +101,12 @@ You have a Kubernetes environment that produces 5k time series per second with 1
 VictoriaMetrics requires additional disk space for the index. The lower Churn Rate means lower disk space usage for the index because of better compression.
 Usually, the index takes about 20% of the disk space for storing data. High cardinality setups may use >50% of datapoints storage size for index.
 
-You can significantly reduce the amount of disk usage by specifying [Downsampling](https://docs.victoriametrics.com/#downsampling) and [Retention Filters](https://docs.victoriametrics.com/#retention-filters) that are lower than the Retention Period. Both two settings are available in Managed VictoriaMetrics and Enterprise.
+You can significantly reduce the amount of disk usage by specifying [Downsampling](https://docs.victoriametrics.com/#downsampling) and [Retention Filters](https://docs.victoriametrics.com/#retention-filters) that are lower than the Retention Period. Both two settings are available in VictoriaMetrics Cloud and Enterprise.
 
 
 ## Align Terms with VictoriaMetrics setups
 
-### Managed VictoriaMetrics
+### VictoriaMetrics Cloud
 
 Every deployment (Single-Node or Cluster) contains the expected load in Ingestion Rate and Active Time Series. We assume that the Churn Rate is no more than 30%. You may need to choose a more extensive deployment if you have a higher Churn Rate.
 

docs/managed-victoriametrics/README.md

@@ -1,14 +0,0 @@
-* [Overview of Managed VictoriaMetrics](/managed-victoriametrics/overview/)
-* [Quick Start](/managed-victoriametrics/quickstart/)
-
-## Guides
-* [Understand Your Setup Size](/guides/understand-your-setup-size/)
-* [Alerting & recording rules with Alertmanager configuration for Managed VictoriaMetrics deployment](/managed-victoriametrics/alertmanager-setup-for-deployment/)
-* [Kubernetes Monitoring with Managed VictoriaMetrics](/managed-victoriametrics/how-to-monitor-k8s/)
-* [Setup Notifications](/managed-victoriametrics/setup-notifications/)
-* [User Management](/managed-victoriametrics/user-managment/)
-
-Learn more about Managed VictoriaMetrics:
-* [Managed VictoriaMetrics announcement](https://victoriametrics.com/blog/managed-victoriametrics-announcement)
-* [Pricing comparison for Managed Prometheus](https://victoriametrics.com/blog/managed-prometheus-pricing/)
-* [Monitoring Proxmox VE via Managed VictoriaMetrics and vmagent](https://victoriametrics.com/blog/proxmox-monitoring-with-dbaas/)

docs/managed-victoriametrics/_index.md

@@ -1,7 +0,0 @@
----
-sort: 28
-title: Managed VictoriaMetrics
-weight: 01
-disableToc: true
----
-{{% content "README.md" %}}

docs/victoriametrics-cloud/README.md

@@ -0,0 +1,14 @@
+* [Overview of VictoriaMetrics Cloud](/victoriametrics-cloud/overview/)
+* [Quick Start](/victoriametrics-cloud/quickstart/)
+
+## Guides
+* [Understand Your Setup Size](/guides/understand-your-setup-size/)
+* [Alerting & recording rules with Alertmanager configuration for VictoriaMetrics Cloud deployment](/victoriametrics-cloud/alertmanager-setup-for-deployment/)
+* [Kubernetes Monitoring with VictoriaMetrics Cloud](/victoriametrics-cloud/how-to-monitor-k8s/)
+* [Setup Notifications](/victoriametrics-cloud/setup-notifications/)
+* [User Management](/victoriametrics-cloud/user-managment/)
+
+Learn more about VictoriaMetrics Cloud:
+* [VictoriaMetrics Cloud announcement](https://victoriametrics.com/blog/introduction-to-managed-monitoring/)
+* [Pricing comparison for Managed Prometheus](https://victoriametrics.com/blog/managed-prometheus-pricing/)
+* [Monitoring Proxmox VE via VictoriaMetrics Cloud and vmagent](https://victoriametrics.com/blog/proxmox-monitoring-with-dbaas/)

docs/victoriametrics-cloud/_index.md

@@ -0,0 +1,10 @@
+---
+sort: 28
+title: VictoriaMetrics Cloud
+weight: 01
+disableToc: true
+aliases:
+  - /victoriametrics-cloud/index.html
+  - /managed-victoriametrics/index.html
+---
+{{% content "README.md" %}}

docs/victoriametrics-cloud/alerting-vmalert-victoria-metrics-cloud.md

@@ -1,23 +1,25 @@
 ---
 sort: 5
 weight: 5
-title: Alerting with vmalert and Managed VictoriaMetrics
+title: Alerting with vmalert and VictoriaMetrics Cloud
 menu:
   docs:
-    parent: "managed"
+    parent: "cloud"
     weight: 5
 aliases:
-- /managed-victoriametrics/alerting-vmalert-managed-victoria-metrics.html
+  - /victoriametrics-cloud/alerting-vmalert-victoria-metrics-cloud/index.html
+  - /managed-victoriametrics/alerting-vmalert-victoria-metrics-cloud/index.html
 ---
-This guide explains the different ways in which you can use vmalert in conjunction with Managed VictoriaMetrics
 
-![Metrics setup](alerting-vmalert-managed-victoria-metrics_setup.webp)
+This guide explains the different ways in which you can use vmalert in conjunction with VictoriaMetrics Cloud
+
+![Metrics setup](alerting-vmalert-victoria-metrics-cloud_setup.webp)
 
 ## Preconditions 
 
 * [vmalert](https://docs.victoriametrics.com/vmalert/) is installed. You can obtain it by building it from [source](https://docs.victoriametrics.com/vmalert/#quickstart), downloading it from the [GitHub releases page](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/latest), or using the [docker image](https://hub.docker.com/r/victoriametrics/vmalert) for the container ecosystem (such as docker, k8s, etc.).
 * [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) is installed.
-* You have a [single or cluster](https://docs.victoriametrics.com/managed-victoriametrics/quickstart.html#creating-deployment) deployment in [Managed VictoriaMetrics](https://docs.victoriametrics.com/managed-victoriametrics/overview.html).
+* You have a [single or cluster](https://docs.victoriametrics.com/victoriametrics-cloud/quickstart.html#creating-deployment) deployment in [VictoriaMetrics Cloud](https://docs.victoriametrics.com/victoriametrics-cloud/overview.html).
 * If you are using helm, add the [VictoriaMetrics helm chart](https://github.com/VictoriaMetrics/helm-charts/tree/master/charts/victoria-metrics-alert#how-to-install) repository to your helm repositories. This step is optional.
 * If you are using [vmoperator](https://docs.victoriametrics.com/operator/quick-start.html#quick-start), make sure that it and its CRDs are installed. This step is also optional.
 
@@ -45,22 +47,22 @@ groups:
         description: "Job {{ $labels.job }}  instance: {{$labels.instance }} is not up for the last 1 minute"
 ```
 
-### Managed VictoriaMetrics access token and deployment endpoint
+### VictoriaMetrics Cloud access token and deployment endpoint
 
-To use vmalert with Managed VictoriaMetrics, you must create a read/write token, or use an existing one. The token must have write access to ingest recording rules, ALERTS and ALERTS_FOR_STATE metrics, and read access for rules evaluation.
+To use vmalert with VictoriaMetrics Cloud, you must create a read/write token, or use an existing one. The token must have write access to ingest recording rules, ALERTS and ALERTS_FOR_STATE metrics, and read access for rules evaluation.
 
-For instructions on how to create tokens, please refer to this section of the [documentation](https://docs.victoriametrics.com/managed-victoriametrics/quickstart.html#deployment-access).
+For instructions on how to create tokens, please refer to this section of the [documentation](https://docs.victoriametrics.com/victoriametrics-cloud/quickstart.html#deployment-access).
 
 #### Single-Node
 
-![Token created single](alerting-vmalert-managed-victoria-metrics_token_created_single.webp)
-![Copy datasource single](alerting-vmalert-managed-victoria-metrics_copy_datasource_single.webp)
+![Token created single](alerting-vmalert-victoria-metrics-cloud_token_created_single.webp)
+![Copy datasource single](alerting-vmalert-victoria-metrics-cloud_copy_datasource_single.webp)
 
 #### Cluster
 
-![Token created cluster](alerting-vmalert-managed-victoria-metrics_token_created_cluster.webp)
-![Reading datasource cluster](alerting-vmalert-managed-victoria-metrics_copy_reading_datasource_cluster.webp)
-![Writing atasource cluster](alerting-vmalert-managed-victoria-metrics_copy_writing_datasource_cluster.webp)
+![Token created cluster](alerting-vmalert-victoria-metrics-cloud_token_created_cluster.webp)
+![Reading datasource cluster](alerting-vmalert-victoria-metrics-cloud_copy_reading_datasource_cluster.webp)
+![Writing atasource cluster](alerting-vmalert-victoria-metrics-cloud_copy_writing_datasource_cluster.webp)
 
 ### vmalert configuration 
 

docs/victoriametrics-cloud/alertmanager-setup-for-deployment.md

@@ -1,15 +1,16 @@
 ---
 sort: 4
 weight: 4
-title: Alertmanager and VMAlert configuration for Managed VictoriaMetrics deployment
+title: Alertmanager and VMAlert configuration for VictoriaMetrics Cloud deployment
 menu:
   docs:
-    parent: "managed"
+    parent: "cloud"
     weight: 4
 aliases:
-  - /managed-victoriametrics/alertmanager-setup-for-deployment.html
+  - /victoriametrics-cloud/alertmanager-setup-for-deployment/index.html
+  - /managed-victoriametrics/alertmanager-setup-for-deployment/index.html
 ---
-Managed VictoriaMetrics supports configuring alerting rules, powered by vmalert, and sending notifications with hosted Alertmanager.
+VictoriaMetrics Cloud supports configuring alerting rules, powered by vmalert, and sending notifications with hosted Alertmanager.
 
 ## Configure Alertmanager
 
@@ -37,7 +38,7 @@ Alertmanager is now set up for your deployment, and you be able to get notificat
 
 ### Alertmanager config specification
 
-Managed VictoriaMetrics supports Alertmanager with standard [configuration specification](https://prometheus.io/docs/alerting/latest/configuration/).
+VictoriaMetrics Cloud supports Alertmanager with standard [configuration specification](https://prometheus.io/docs/alerting/latest/configuration/).
 
 But with respect to the specification, there are the following limitations:
 
@@ -122,7 +123,7 @@ receivers:
 
 ### Custom Alertmanager
 
-If for some reason Cloud Alertmanager is not suitable for you, you can use Managed VictoriaMetrics with any external Alertmanager hosted in your infrastructure.
+If for some reason Cloud Alertmanager is not suitable for you, you can use VictoriaMetrics Cloud with any external Alertmanager hosted in your infrastructure.
 
 For that select Custom Alertmanager instead of Cloud Alertmanager when [creating the Alertmanager](#configure-alertmanager):
 

docs/victoriametrics-cloud/how-to-monitor-k8s.md

@@ -1,13 +1,14 @@
 ---
 sort: 3
 weight: 3
-title: Kubernetes Monitoring with Managed VictoriaMetrics
+title: Kubernetes Monitoring with VictoriaMetrics Cloud
 menu:
   docs:
-    parent: "managed"
+    parent: "cloud"
     weight: 3
 aliases:
-- /managed-victoriametrics/how-to-monitor-k8s.html
+  - /victoriametrics-cloud/how-to-monitor-k8s/index.html
+  - /managed-victoriametrics/how-to-monitor-k8s/index.html
 ---
 Monitoring kubernetes cluster is necessary to build SLO/SLI, to analyze performance and cost-efficiency of your workloads. 
 
@@ -24,7 +25,8 @@ This chart will install `VMOperator`, `VMAgent`, `NodeExporter`, `kube-state-met
 
 ## Prerequisites
 
-- Active Managed VictoriaMetrics instance. You can learn how to sign up for Managed VictoriaMetrics [here](https://docs.victoriametrics.com/managed-victoriametrics/quickstart.html#how-to-register). 
+
+- Active VictoriaMetrics Cloud instance. You can learn how to sign up for VictoriaMetrics Cloud [here](https://docs.victoriametrics.com/victoriametrics-cloud/quickstart.html#how-to-register).
 - Access to your kubernetes cluster
 - Helm binary. You can find installation [here](https://helm.sh/docs/intro/install/)
 

docs/victoriametrics-cloud/overview.md

@@ -1,13 +1,14 @@
 ---
 sort: 1
 weight: 1
-title: Overview of Managed VictoriaMetrics 
+title: Overview of VictoriaMetrics Cloud 
 menu:
   docs:
-    parent: "managed"
+    parent: "cloud"
     weight: 1
 aliases:
-- /managed-victoriametrics/overview.html
+  - /victoriametrics-cloud/overview/index.html
+  - /managed-victoriametrics/overview/index.html
 ---
 VictoriaMetrics is a fast and easy-to-use monitoring solution and time series database. 
 It integrates well with existing monitoring systems such as Grafana, Prometheus, Graphite, 
@@ -19,20 +20,20 @@ The most common use cases for VictoriaMetrics are:
 * Replacement for InfluxDB and OpenTSDB, which uses lower amounts of RAM, CPU and disk;
 * Cost-efficient alternative for DataDog.
 
-Managed VictoriaMetrics allows users to run Enterprise version of VictoriaMetrics, hosted on AWS, without the need to perform typical 
+VictoriaMetrics Cloud allows users to run Enterprise version of VictoriaMetrics, hosted on AWS, without the need to perform typical 
 DevOps tasks such as proper configuration, monitoring, logs collection, access protection, software updates, 
 backups, etc. [Try it right now](https://cloud.victoriametrics.com/signUp?utm_source=website&utm_campaign=docs_overview)
 
-We run Managed VictoriaMetrics deployments in our environment on AWS and provide easy-to-use endpoints 
+We run VictoriaMetrics Cloud deployments in our environment on AWS and provide easy-to-use endpoints 
 for data ingestion and querying. The VictoriaMetrics team takes care of optimal configuration and software 
 maintenance.
 
-Managed VictoriaMetrics comes with the following features:
+VictoriaMetrics Cloud comes with the following features:
 
-* It can be used as a Managed Prometheus - just configure Prometheus or vmagent to write data to Managed VictoriaMetrics and then use the provided endpoint as a Prometheus datasource in Grafana;
-* Built-in [Alerting & Recording](https://docs.victoriametrics.com/managed-victoriametrics/alertmanager-setup-for-deployment/#configure-alerting-rules) rules execution;
-* Hosted [Alertmanager](https://docs.victoriametrics.com/managed-victoriametrics/alertmanager-setup-for-deployment/) for sending notifications;
-* Every Managed VictoriaMetrics deployment runs in an isolated environment, so deployments cannot interfere with each other;
-* Managed VictoriaMetrics deployment can be scaled up or scaled down in a few clicks;
+* It can be used as a Managed Prometheus - just configure Prometheus or vmagent to write data to VictoriaMetrics Cloud and then use the provided endpoint as a Prometheus datasource in Grafana;
+* Built-in [Alerting & Recording](https://docs.victoriametrics.com/victoriametrics-cloud/alertmanager-setup-for-deployment/#configure-alerting-rules) rules execution;
+* Hosted [Alertmanager](https://docs.victoriametrics.com/victoriametrics-cloud/alertmanager-setup-for-deployment/) for sending notifications;
+* Every VictoriaMetrics Cloud deployment runs in an isolated environment, so deployments cannot interfere with each other;
+* VictoriaMetrics Cloud deployment can be scaled up or scaled down in a few clicks;
 * Automated backups;
 * Pay only for the actually used resources - compute, storage, traffic.

docs/victoriametrics-cloud/quickstart.md

@@ -4,12 +4,13 @@ weight: 2
 title: Quick Start
 menu:
   docs:
-    parent: "managed"
+    parent: "cloud"
     weight: 2
 aliases:
-- /managed-victoriametrics/quickstart.html
+  - /victoriametrics-cloud/quickstart/index.html
+  - /managed-victoriametrics/quickstart/index.html
 ---
-Managed VictoriaMetrics is a hosted monitoring platform, where users can run the VictoriaMetrics 
+VictoriaMetrics Cloud is a hosted monitoring platform, where users can run the VictoriaMetrics 
 that they know and love on AWS without the need to perform typical DevOps tasks such as proper configuration, 
 monitoring, logs collection, access protection, software updates, backups, etc.
 
@@ -37,7 +38,7 @@ There are two different methods to create an account:
 1. Choose Google account you want to use for registration
 ![Signup Google choose account](quick_start_signup_choose_google_account.webp)
 
-1. You will be automatically redirected to the main page of the Managed VictoriaMetrics
+1. You will be automatically redirected to the main page of the VictoriaMetrics Cloud
 ![Signup success](quick_start_signup_success.webp)
 
 ### Create an account by filling in a registration form:
@@ -102,12 +103,12 @@ When you need to unify your AWS billing, you can start a subscription on AWS Mar
    
      ![Add payment method AWS click](how_to_add_payment_method_aws_click.webp)
    
-1. You will be redirected to the <a href="https://aws.amazon.com/marketplace/pp/prodview-4tbfq5icmbmyc" target="_blank">Managed VictoriaMetrics</a> product page.
+1. You will be redirected to the <a href="https://aws.amazon.com/marketplace/pp/prodview-4tbfq5icmbmyc" target="_blank">VictoriaMetrics Cloud</a> product page.
 1. Click on `View purchase option` button, and you will be redirected to an AWS login page or to a subscribe page on AWS Marketplace.
    
      ![AWS purchase click](quickstart_aws-purchase-click.webp)
    
-1. Go to the <a href="https://aws.amazon.com/marketplace/pp/prodview-4tbfq5icmbmyc">Managed VictoriaMetrics</a> product page and click `Continue to Subscribe` button:
+1. Go to the <a href="https://aws.amazon.com/marketplace/pp/prodview-4tbfq5icmbmyc">VictoriaMetrics Cloud</a> product page and click `Continue to Subscribe` button:
    
      ![Continue subscribe](quickstart_continue-subscribe.webp)
    
@@ -119,7 +120,7 @@ When you need to unify your AWS billing, you can start a subscription on AWS Mar
    
      ![Setup your account](quickstart_setup-your-account.webp)
    
-1. You'll be redirected back to Managed VictoriaMetrics <a href="https://cloud.victoriametrics.com/billing?utm_source=website&utm_campaign=docs_quickstart" target="_blank">billing page</a>:
+1. You'll be redirected back to VictoriaMetrics Cloud <a href="https://cloud.victoriametrics.com/billing?utm_source=website&utm_campaign=docs_quickstart" target="_blank">billing page</a>:
    
      ![Add payment method finish](how_to_add_payment_method_aws_finish.webp)
    
@@ -161,7 +162,7 @@ If you forgot your password, it can be restored in the following way:
      ![Restore password message](quick_start_restore_password_message.webp)
    
 
-1. Follow the instructions sent to your email in order to get access to your Managed VictoriaMetrics account:
+1. Follow the instructions sent to your email in order to get access to your VictoriaMetrics Cloud account:
    
      ![Restore password email](quick_start_restore_password_email.webp)
    
@@ -221,7 +222,7 @@ You'll also be notified via email once your deployment is ready to use:
 
 ## Start writing and reading data
 
-After transition from `PROVISIONING` to `RUNNING` state, Managed VictoriaMetrics deployment is fully operational 
+After transition from `PROVISIONING` to `RUNNING` state, VictoriaMetrics Cloud deployment is fully operational 
 and is ready to accept write and read requests. 
 
 Click on deployment name and navigate to the Access tab to get the access token:

docs/victoriametrics-cloud/setup-notifications.md

@@ -1,13 +1,14 @@
 ---
 sort: 7
 weight: 7
-title: Notifications in Managed VictoriaMetrics
+title: Notifications in VictoriaMetrics Cloud
 menu:
   docs:
-    parent: "managed"
+    parent: "cloud"
     weight: 7
 aliases:
-- /managed-victoriametrics/setup-notifications.html
+  - /victoriametrics-cloud/setup-notifications/index.html
+  - /managed-victoriametrics/setup-notifications/index.html
 ---
 The guide covers how to enable email and Slack notifications.
 

docs/victoriametrics-cloud/user-managment.md

@@ -1,15 +1,16 @@
 ---
 sort: 6
 weight: 6
-title: User Management in Managed VictoriaMetrics
+title: User Management in VictoriaMetrics Cloud
 menu:
   docs:
-    parent: "managed"
+    parent: "cloud"
     weight: 6
 aliases:
-- /managed-victoriametrics/user-management.html
+  - /victoriametrics-cloud/user-management/index.html
+  - /managed-victoriametrics/user-management/index.html
 ---
-The user management system enables admins to control user access and onboard and offboard users to the Managed VictoriaMetrics. It organizes users according to their needs and role.
+The user management system enables admins to control user access and onboard and offboard users to the VictoriaMetrics Cloud. It organizes users according to their needs and role.
 
 The document covers the following topics
 1. [User Roles](#user-roles)
@@ -20,7 +21,7 @@ The document covers the following topics
 
 ## User roles
 
-Managed VictoriaMetrics provides different levels of user access. It defines what information users can access and edit in your account.
+VictoriaMetrics Cloud provides different levels of user access. It defines what information users can access and edit in your account.
 
 You assign the role to the user during the user creation procedure. You can change the role after the creation
 
@@ -86,7 +87,7 @@ You assign the role to the user during the user creation procedure. You can chan
 <table class="params">
   <tr>
    <td class="highlight"><strong class="sr">Active</strong></td>
-   <td>The user can log in and use Managed VictoriaMetrics. The user role defines the access level.</td>
+   <td>The user can log in and use VictoriaMetrics Cloud. The user role defines the access level.</td>
   </tr>
   <tr>
    <td class="highlight"><strong class="s1">Pending Invitation</strong></td>
@@ -94,7 +95,7 @@ You assign the role to the user during the user creation procedure. You can chan
   </tr>
   <tr>
    <td class="highlight"><strong class="nn">Inactive</strong></td>
-   <td>The user is registered in the Managed VictoriaMetrics but has no access to perform any actions. Admin can activate or completely delete the user.</td>
+   <td>The user is registered in the VictoriaMetrics Cloud but has no access to perform any actions. Admin can activate or completely delete the user.</td>
   </tr>
 </table>
 
@@ -127,7 +128,7 @@ In the table, there is additional information about the users:
   </tr>
   <tr>
    <td>Auth method:</td>
-   <td>Auth options to login into the Managed VictoriaMetrics</td>
+   <td>Auth options to login into the VictoriaMetrics Cloud</td>
   </tr>
 </table>