Feature/project prince jacob (github#493)

* initial setup

* remove update search index for now

* major overhaul - links to console and new portal not changed

* index page for mst

* mst-multi-node

* finish mst section content

* convert forge links

* General edits for wording, etc. (github#381)

* update (github#386)

* Add command to install timescaledb-tools (github#364)

* Fix missing semi-colon (github#363)

Co-authored-by: Jacob Prall <prall.jacob@gmail.com>

* Remove 'repeatable' isolation level from multinode docs (github#361)

Co-authored-by: Jacob Prall <prall.jacob@gmail.com>

* Fix bad path (github#360)

* add leading slash

* Add version

* typo

Co-authored-by: Jacob Prall <prall.jacob@gmail.com>

* Update install instructions (github#359)

* Update install instructions

* Change postgres to timescaledb repo

* Add sudo

* Remove extra whitespace

* Update to correct key

* Edits per feedback

* Add step to install postgres repo

* Apply suggestions from code review

Co-authored-by: Cam Hutchison <35285934+camscale@users.noreply.github.com>

Co-authored-by: Cam Hutchison <35285934+camscale@users.noreply.github.com>
Co-authored-by: Jacob Prall <prall.jacob@gmail.com>

* Fix/link checker error (github#370)

* add absolute path to links

* add slash

* Fix incorrect sql query (github#362)

Co-authored-by: Jacob Prall <prall.jacob@gmail.com>

* Add the toolkit as a pre-req to the tutorial. (github#306)

* Add the toolkit as a pre-req to the tutorial.

* Fix link in admon

* Point to correct URL

* fix link

Co-authored-by: Jacob Prall <prall.jacob@gmail.com>

* Fix/link checker error (github#374)

* add absolute path to links

* add slash

* add base url

* add new to ignore

* Fix/link checker error (github#376)

* add absolute path to links

* add slash

* add base url

* add new to ignore

* add scheme

* Document the differences between time_bucket() and time_bucket_ng() (github#354)

Document the differences between time_bucket() and time_bucket_ng()

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update install instructions (github#379)

* Update install instructions

* Update timescaledb/how-to-guides/install-timescaledb/installation-apt-debian.md

Co-authored-by: Jacob Prall <prall.jacob@gmail.com>

* Add metadata for tutorials (github#380)

* Add metadata for tutorials

* Update page-index.js

typo correction

Co-authored-by: Jacob Prall <prall.jacob@gmail.com>

* Update page-index.js

Co-authored-by: Lana Brindley <github@lanabrindley.com>
Co-authored-by: Cam Hutchison <35285934+camscale@users.noreply.github.com>
Co-authored-by: Aleksander Alekseev <mail@eax.me>

* change to cloud

* cloud

* Update time_bucket_ng.md (github#417)

* Update cloud/cloud-multi-node.md

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update cloud/create-a-service.md

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update mst/create-a-service.md

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update timescaledb/tutorials/setting-up-mst-for-prometheus.md

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update timescaledb/tutorials/setting-up-mst-for-prometheus.md

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update timescaledb/tutorials/setting-up-mst-for-prometheus.md

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update timescaledb/tutorials/setting-up-mst-for-prometheus.md

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update timescaledb/tutorials/setting-up-mst-for-prometheus.md

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update cloud/create-a-service.md

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update time_bucket_ng.md

* Update cloud/create-a-service.md

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* update portal managed

* Feature/timescale license comparison (github#453)

* added timescale license comparison

* edit title

* update

* Make sure window functions are listed as unsupported (github#393)

Co-authored-by: Jacob Prall <prall.jacob@gmail.com>

* update link (github#420)

* update (github#422)

* Fix/update link checker (github#424)

* update

* don't check if starts with /

* add excludes (github#426)

* Fix/linkchecker (github#428)

* add excludes

* update

* Fix/linkchecker (github#430)

* add excludes

* update

* update

* Fix/linkchecker (github#432)

* add excludes

* update

* update

* comment out link checker

* Fix/link checker again (github#433)

* try to include link checker

* reinstate index rebuild on merge

* tweak yaml

* remove link detector

* tweak curl

* remove link checker

* remove search index from deploy

* tweak update search

* update search index

* change name of action

* stop search index for now

* ignore search update

* remove update search index

* Add .NET C# quick start tutorial (github#412)

* Add C# dotnet quickstart

* Update dotnet.md

Fixing steps to have numbers, a few heading formatting issues, and changing the "step" text above each method.

* Apply suggestions from code review

Applying most changes. I want to verify that auto numbering will work across code sections before accepting those.

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Apply suggestions from code review

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update dotnet.md

Co-authored-by: Ryan Booz <ryan@timescale.com>
Co-authored-by: Lana Brindley <github@lanabrindley.com>

* update copy

* update copy

* add edition

* Fix typo in JSON docs (github#441)

Co-authored-by: Tadas Malinauskas <tadas.malinauskas@oxylabs.io>

* Clarify behavior when deleting a data node (github#406)

* Clarify behavior when deleting a data node

When deleting a data node, the database (including its data) on the
data node is left intact. This sometimes confuses users and this
change clarifies this behavior and adds explanations for why this
behavior exists.

* Update api/delete_data_node.md

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update api/delete_data_node.md

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Apply suggestions from code review

minor copy edits

Co-authored-by: Lana Brindley <github@lanabrindley.com>

Co-authored-by: Jacob Prall <prall.jacob@gmail.com>
Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update README.md

add newLabel to page-index read me

* Add link to developer docs on GH (github#438)

* Add link to developer docs on GH

* Add link to developer docs on install page

* remove new item

Co-authored-by: Lana Brindley <github@lanabrindley.com>
Co-authored-by: Jônatas Davi Paganini <jonatasdp@gmail.com>
Co-authored-by: Ryan Booz <ryan@timescale.com>
Co-authored-by: Tadas Malinauskas <Taadas@users.noreply.github.com>
Co-authored-by: Tadas Malinauskas <tadas.malinauskas@oxylabs.io>
Co-authored-by: Erik Nordström <819732+erimatnor@users.noreply.github.com>

* Update timescaledb-license-comparison.md

* update timescale table

* add terms of service links

* update

* add terms of service links

* Update timescaledb-license-comparison.md

* Update timescaledb-license-comparison.md

Co-authored-by: Lana Brindley <github@lanabrindley.com>
Co-authored-by: Cam Hutchison <35285934+camscale@users.noreply.github.com>
Co-authored-by: Aleksander Alekseev <mail@eax.me>
Co-authored-by: Jônatas Davi Paganini <jonatasdp@gmail.com>
Co-authored-by: Ryan Booz <ryan@timescale.com>
Co-authored-by: Tadas Malinauskas <Taadas@users.noreply.github.com>
Co-authored-by: Tadas Malinauskas <tadas.malinauskas@oxylabs.io>
Co-authored-by: Erik Nordström <819732+erimatnor@users.noreply.github.com>

api/page-index/page-index.js

@@ -407,9 +407,9 @@ module.exports = [
             href: 'jobs',
           },
           {
-            title: "timescaledb_information.job_stats",
-            href: "job_stats"
-          }
+            title: 'timescaledb_information.job_stats',
+            href: 'job_stats',
+          },
         ],
       },
       {

api/time_bucket_ng.md

@@ -54,6 +54,7 @@ timezone and so the function can't be used with continuous aggregates.
 The function returns the bucket's start time. The return value type is the
 same as `ts`.
 
+
 ### Sample Usage
 
 In this example, `time_bucket_ng()` is used to create bucket data in three month

timescale-forge/forge-multi-node.md → cloud/cloud-multi-node.md

@@ -1,25 +1,25 @@
-# Setting up TimescaleDB 2.0 multi-node on Timescale Forge
+# Setting up TimescaleDB 2.0 multi-node on Timescale Cloud
 TimescaleDB 2.0 [introduces a number of new features][changes-in-tsdb2] to
 supercharge time-series data even further. One of the most anticipated new
 features is what we call **multi-node** - the ability to create a cluster of
 TimescaleDB instances to scale both reads and writes.
 
-In this How To, we’ll show you how to create a multi-node cluster in your
-Timescale Forge account using TimescaleDB 2.0.
+In this How To, we'll show you how to create a multi-node cluster in your
+Timescale Cloud account using TimescaleDB 2.0.
 
-This document details a "do-it-yourself" (DIY) multi-node experience on Forge.
+This document details a "do-it-yourself" (DIY) multi-node experience on Cloud.
 In the future, we will offer a seamless point-and-click multi-node
-experience within the Timescale Forge console UI, but we wanted to provide a way
+experience within the Timescale Cloud console UI, but we wanted to provide a way
 for users to setup and test this feature before that interface is available.
 
 If you’re ready to set up a TimescaleDB multi-node cluster as part of your
-Timescale Forge account, continue on! If you want to follow along but don't
-yet have a Timescale Forge account, [sign-up today for a 100% free, 30-day
+Timescale Cloud account, continue on! If you want to follow along but don't
+yet have a Timescale Cloud account, [sign-up today for a 100% free, 30-day
 trial][sign-up]!
 
 ## Overview of multi-node setup
 Multi-node clusters consist of at least two or more TimescaleDB instances
-(called **Services** in Timescale Forge). Each cluster has one access node
+(called **Services** in Timescale Cloud). Each cluster has one access node
 (AN) and one or more data nodes (DN). As outlined in our
 [architecture blog posts][distributed-architechture], the access node is
 intended to be the only TimescaleDB instance that you or your applications
@@ -35,20 +35,20 @@ single-node TimescaleDB instance and is not recommended.
 </highlight>
 
 ### Create services for access and data nodes
-First, you need to create new Services within your Forge account. As mentioned
+First, you need to create new Services within your Cloud account. As mentioned
 earlier, you should create _at least_ three Services to set up a multi-node
 cluster: one access node and two data nodes.
 
 There is currently no way to distinguish between the access node and data nodes
-within the Timescale Forge console, so we strongly recommend that you include
+within the Timescale Cloud console, so we strongly recommend that you include
 "an" and "dn" in the names of each service, respectively. For example, use
 "an-mycluster", "dn1-mycluster", and "dn2-mycluster". To prevent problems later
 on, always use all lowercase names for your new nodes. Services can only assume
 one role in a cluster (access or data node), and only one Service can act as the
 access node.
 
 For simplicity you can start with the same hardware configuration for all
-Services. On Timescale Forge, Service configuration can be modified later to
+Services. On Timescale Cloud, Service configuration can be modified later to
 better tune access and data node requirements.
 
 <highlight type="tip">
@@ -72,7 +72,7 @@ distributed planning process.
 
 To that end, we highly recommend these settings be modified for the **Access
 Node** only under the **Settings** tab, shown in the
-[Customize database configuration][forge-configuration] documentation.
+[Customize database configuration][cloud-configuration] documentation.
 
 *   `jit` = off
 *   `max_prepared_transactions` > 0 (150 is a recommended starting value)
@@ -84,13 +84,13 @@ access node and all data nodes. The currently supported method for securing
 communication between nodes is through **user mapping authentication**.
 
 This is also a manual process for now. As we continue to develop Timescale
-Forge and multi-node functionality, this process will be a much smoother user
-experience, completed directly from the Timescale Forge Console.
+Cloud and multi-node functionality, this process will be a much smoother user
+experience, completed directly from the Timescale Cloud Console.
 
 #### About user mapping authentication
 User mapping authentication allows users to continue connecting with the
 `tsdbadmin` PostgreSQL user for all data access and cluster management. It also
-allows you to continue making secure (SSL) connections to your Timescale Forge
+allows you to continue making secure (SSL) connections to your Timescale Cloud
 Access node.
 
 With user mapping authentication, you don’t need to manage any new users,
@@ -242,12 +242,12 @@ data.
 And as always, consider joining our vibrant community [Slack channel][slack] to
 ask questions and learn from Timescale staff and other community members.
 
-[sign-up]: https://forge.timescale.com/signup
+[sign-up]: https://console.cloud.timescale.com/signup
 [maintenance-tasks]: timescaledb/:currentVersion:/how-to-guides/multi-node-setup/maintenance-tasks/
 [slack]: https://slack.timescale.com/
 [changes-in-tsdb2]: /timescaledb/:currentVersion:/overview/release-notes/changes-in-timescaledb-2
 [distributed-architechture]: https://blog.timescale.com/blog/building-a-distributed-time-series-database-on-postgresql/
 [postgres-user-mapping]: https://www.postgresql.org/docs/current/view-pg-user-mappings.html
 [sample-data]: /timescaledb/:currentVersion:/tutorials/sample-datasets
 [promscale]: https://github.com/timescale/promscale
-[forge-configuration]: /customize-configuration
+[cloud-configuration]: /customize-configuration

timescale-forge/create-a-service.md → cloud/create-a-service.md

@@ -1,11 +1,11 @@
-# Exploring Timescale Forge
-Welcome to Timescale Forge! Timescale Forge is a cloud-native TimescaleDB as a
+# Exploring Timescale Cloud
+Welcome to Timescale Cloud! Timescale Cloud is a cloud-native TimescaleDB as a
 service that is easy to get started and powerful enough for the most demanding
-scenarios. This tutorial walks you through setting up your Timescale Forge
+scenarios. This tutorial walks you through setting up your Timescale Cloud
 account and completing your first tutorial project.
 
-### Create a Timescale Forge account
-Sign up for Timescale Forge by visiting [forge.timescale.com][forge-signup].
+### Create a Timescale Cloud account
+Sign up for Timescale Cloud by visiting [console.cloud.timescale.com][cloud-signup].
 Provide your full name, email address, and a strong password to start:
 
 <img class="main-content__illustration" src="https://assets.iobeam.com/images/docs/forge_images/timescale-forge-signup-page.png" alt="Sign up for Timescale Forge"/>
@@ -16,7 +16,7 @@ If you do not receive this link, check your spam folder first, then
 
 ### Create your first service
 When you have completed account verification, visit the
-[Timescale Forge console][forge-console] and login with your credentials.
+[Timescale Cloud console][cloud-console] and login with your credentials.
 
 To begin, click `Create service`.
 
@@ -34,11 +34,11 @@ To begin, click `Create service`.
 1.  Click `Create service` when your configuration is complete.
 
 <highlight type="tip">
-Don't worry if too much about the size settings that you choose initially.
-With Timescale Forge, it's easy to modify both the compute (CPU/Memory) and
+Don't worry too much about the size settings that you choose initially.
+With Timescale Cloud, it's easy to modify both the compute (CPU/Memory) and
 storage associated with the service that you just created. As you get to know
 TimescaleDB and how your data processing needs vary, it's easy to [right-size
-your service with a few clicks](/timescale-forge/latest/scaling-a-service/)!
+your service with a few clicks](/cloud/latest/scaling-a-service/)!
 </highlight>
 
 After you select `Create service`, you will see confirmation of your service
@@ -66,7 +66,7 @@ a service altogether.
 <img class="main-content__illustration" src="https://assets.iobeam.com/images/docs/forge_images/forge_running-service.png" alt="View Timescale Forge service information"/>
 
 ### Complete your first tutorial
-Congratulations! You are now up and running with Timescale Forge. To
+Congratulations! You are now up and running with Timescale Cloud. To
 familiarize yourself with the features and capabilities of the product, we
 recommend that you complete the [Getting Started][getting-started] tutorial.
 
@@ -81,7 +81,7 @@ Read about TimescaleDB features in our documentation:
 ### Keep testing during your free trial
 You’re now on your way to a great start with Timescale!
 
-You will have an unthrottled, 30-day free trial with Timescale Forge to
+You will have an unthrottled, 30-day free trial with Timescale Cloud to
 continue to test your use case. Before the end of your trial, we encourage you
 to add your credit card information. This will ensure a smooth transition after
 your trial period concludes.
@@ -93,23 +93,23 @@ feel free to [join our community Slack group][slack-info]
 or [contact us][contact-timescale] directly.
 
 ## Advanced configuration and multi-node setup
-Timescale Forge is a versatile hosting service that provides a growing list of
+Timescale Cloud is a versatile hosting service that provides a growing list of
 advanced features for your PostgreSQL and time-series data workloads.
 
 For additional documentation on how to:
 *   [Resize compute and storage][resize] at any time
 *   [Customize your database configuration][configuration] easily
-*   [Create a TimescaleDB multi-node cluster][multi-node] in Timescale Forge
+*   [Create a TimescaleDB multi-node cluster][multi-node] in Timescale Cloud
 
-[forge-signup]: https://forge.timescale.com
+[cloud-signup]: https://console.cloud.timescale.com
 [slack-info]: https://slack-login.timescale.com
 [getting-started]: /timescaledb/latest/getting-started/
-[forge-console]: https://console.forge.timescale.com/login
+[cloud-console]: https://console.cloud.timescale.com/login
 [contact-timescale]: https://www.timescale.com/contact
 [hypertable-info]: /timescaledb/latest/how-to-guides/hypertables
 [time-bucket-info]: /timescaledb/latest/how-to-guides/query-data/advanced-analytic-queries#time-bucket
 [gap-filling-info]: /timescaledb/latest/how-to-guides/query-data/advanced-analytic-queries#gap-filling
 [aggregates-info]: /timescaledb/latest/getting-started/create-cagg
 [resize]: /scaling-a-service/
 [configuration]: /customize-configuration/
-[multi-node]: /forge-multi-node/
+[multi-node]: /cloud-multi-node/

timescale-forge/customize-configuration.md → cloud/customize-configuration.md

@@ -1,5 +1,5 @@
-# Customize database configuration in Timescale Forge
-Timescale Forge allows you to customize many TimescaleDB and PostgreSQL
+# Customize database configuration in Timescale Cloud
+Timescale Cloud allows you to customize many TimescaleDB and PostgreSQL
 configuration options for each Service individually. Most configuration values
 for a Service are initially set in accordance with best practices given the
 compute and storage settings of the Service. Any time you increase or decrease
@@ -8,12 +8,12 @@ of the new Service.
 
 There are times, however, when your specific workload may require tuning some
 of the many available TimescaleDB and PostgreSQL parameters. By providing the
-ability to tune various runtime settings, Timescale Forge provides the balance
+ability to tune various runtime settings, Timescale Cloud provides the balance
 and flexibility you need when running your workloads in our hosted environment.
 
 <highlight type="warning">
 Modifications of most parameters can be applied without restarting
-the Timescale Forge Service. However, as when modifying the compute resources
+the Timescale Cloud Service. However, as when modifying the compute resources
 of a running Service, some settings will require that a restart be performed,
 resulting in some brief downtime (usually about 30 seconds).
 </highlight>
@@ -65,7 +65,7 @@ and the `Apply changes` (or `Restart and apply changes`) button is available to
 click, prompting you to confirm any changes before the Service is modified.
 
 ## PostgreSQL extensions
-You can use PostgreSQL extensions with Timescale Forge. If you run
+You can use PostgreSQL extensions with Timescale Cloud. If you run
 `pg_available_extensions` at the command prompt, the returned list of extensions
 is inaccurate. To see the allowed extensions, use this command instead:
 ```sql

timescale-forge/disk-management.md → cloud/disk-management.md

@@ -1,7 +1,7 @@
 # Disk management
 
-Timescale Forge contains several mechanisms for managing disk space on your
-services. There are four key tasks that Forge performs to handle disk space:
+Timescale Cloud contains several mechanisms for managing disk space on your
+services. There are four key tasks that Cloud performs to handle disk space:
 
 1.  Detect if storage capacity begins to fill up
 1.  Notify you about the growth of storage consumption
@@ -13,7 +13,7 @@ of them.
 
 ## Continuous storage monitoring
 
-Timescale Forge continuously monitors the health and resource consumption of all
+Timescale Cloud continuously monitors the health and resource consumption of all
 database services. You can check your health data by navigating to the `metrics`
 tab in your service dashboard. These metrics are also monitored by the Timescale
 operations team.
@@ -42,7 +42,7 @@ about a particular service.
 If your database continues to increase in size past these thresholds, automated
 overload protection is activated when your disk becomes 99% full. When this
 happens, your database is put into read-only mode, and you receive a
-notification on email and the Timescale Forge console shows the changed status.
+notification on email and the Timescale Cloud console shows the changed status.
 
 When this happens, you can still query your database, but you cannot add any new
 data to it. This is to ensure that your disk does not fill up to 100%, which
@@ -55,15 +55,15 @@ avoid the problem occurring again in the future.
 
 ## Online storage resizing
 
-You can increase your storage size in the Timescale Forge console.
+You can increase your storage size in the Timescale Cloud console.
 
 <highlight type="warning">
 You can only increase your service's storage once every six hours, and you cannot
 currently decrease your storage size once set. 
 </highlight>
 
 ### Procedure: Increasing service resources
-1.  In the Timescale Forge console, navigate to `Services` and click the service
+1.  In the Timescale Cloud console, navigate to `Services` and click the service
 you want to adjust. Navigate to the `Operations` tab, and go to the `Resources`
 section.
 1.  Adjust the sliders for CPU and disk size as required. If you increase the

timescale-forge/index.md → cloud/index.md

@@ -1,11 +1,11 @@
-# Timescale Forge
+# Timescale Cloud
 
-Timescale Forge is a cloud-native TimescaleDB as a service that is easy to get 
+Timescale Cloud is a cloud-native TimescaleDB as a service that is easy to get 
 started and powerful enough for the most demanding scenarios. You can 
-[try Timescale Forge for free][sign-up], no credit card required.
+[try Timescale Cloud for free][sign-up], no credit card required.
 
 ### Cloud-native, easy start, low cost
-Built and operated by the team behind TimescaleDB, Timescale Forge is the 
+Built and operated by the team behind TimescaleDB, Timescale Cloud is the 
 innovative and cost-effective way to store and analyze your time-series data.
  * Spin up your first instance in 30 seconds
  * Decoupled storage and compute options for extreme flexibility
@@ -35,4 +35,8 @@ and extensions.
  * More than 75 popular PostgreSQL extensions including PostGIS, pre-installed
  * Integrated support for Prometheus long-term storage 
 
- [sign-up]: https://console.forge.timescale.com/signup
+For more information on Timescale Cloud's terms of service, visit the [Timescale website][tos].
+
+
+ [sign-up]: https://console.cloud.timescale.com/signup
+ [tos]: https://www.timescale.com/legal/timescale-cloud-terms-of-service

timescale-forge/maintenance.md → cloud/maintenance.md

@@ -1,5 +1,5 @@
 # Maintenance
-On Timescale Forge, minor software updates are handled automatically by us, and you do
+On Timescale Cloud, minor software updates are handled automatically by us, and you do
 not need to perform any actions.
 
 Non-critical software updates are applied during a maintenance window that you
@@ -35,19 +35,19 @@ your maintenance window occur during office hours, so that you can monitor your
 system during the upgrade.
 
 ### Procedure: Adjusting your maintenance window
-1.  [Log in to your Timescale Forge account][cloud-login]. Click the name of the
+1.  [Log in to your Timescale Cloud account][cloud-login]. Click the name of the
     service that you want to manage the maintenance window for.
 1.  In the `Operations` tab, navigate to the `Maintenance` section, and
     click `Change maintenance window`.
 1.  In the `Maintenance` dialog, select the day of the week, the time, and the
     timezone that you want the maintenance window to start. Maintenance windows
     can run for up to four hours.
 1.  Check `Apply new maintenance window to all services` if you want to use the
-    same maintenance window settings for all of your Timescale Forge services.
+    same maintenance window settings for all of your Timescale Cloud services.
 1.  Click `Apply Changes`.
 
 ## Critical updates
 Critical upgrades and security fixes are installed outside normal maintenance
 windows when necessary, and sometimes require a short outage.
 
-[cloud-login]: https://console.forge.timescale.com/login
+[cloud-login]: https://cloud.timescale.com

timescale-forge/page-index/page-index.js → cloud/page-index/page-index.js

@@ -1,10 +1,10 @@
 module.exports = [
   {
-    title: "Timescale Forge",
+    title: "Timescale Cloud",
     filePath: 'index.md',
-    href: "timescale-forge",
-    name: 'Timescale Forge',
-    excerpt: 'Timescale Forge is a fully managed TimescaleDB service that allows you to start querying data in less than a minute!',
+    href: "cloud",
+    name: 'Timescale Cloud',
+    excerpt: 'Timescale Cloud is a fully managed TimescaleDB service that allows you to start querying data in less than a minute!',
     children: [
       {
         title: "Create a service",
@@ -20,7 +20,7 @@ module.exports = [
       },
       {
         title: "Create a multi-node cluster",
-        href: "forge-multi-node"
+        href: "cloud-multi-node"
       },
       {
         title: "VPC peering with AWS",