Merge pull request #314 from G-Core/WEB-5217_preprod

Web 5217 preprod

documentation/cdn/cdn-resource-options/cache/cache-sharding-share-cache-between-cdn-servers.md

@@ -0,0 +1,49 @@
+---
+title: cache-sharding-share-cache-between-cdn-servers
+displayName: Cache Sharding
+order: 60
+toc:
+   --1--Cache Sharding: "what-is-the-cache-sharding-feature"
+   --1--How it works: "how-does-the-cache-sharding-feature-work"
+   --1--Benefits: "what-are-the-benefits-of-using-cache-sharding"
+   --1--How to enable: "how-to-enable-the-cache-sharding-feature"
+pageTitle: Understanding of Cache Sharding CDN | Gcore
+pageDescription: Uncover the benefits of Cache Sharding in CDN servers—enhanced content storage, reduced origin requests, and improved delivery speed.
+---
+# Сache Sharding: share cache between CDN servers
+
+## What is the Cache Sharding feature?
+
+Cache Sharding is a feature that allows some CDN servers—grouped together and in the same Point of presence (PoP)—to use one another’s cache to increase the CDN performance. When users request content, a CDN server proxies a request to another server where the cache is located using a consistent hashing algorithm.
+
+This feature is particularly important for websites and applications with a large amount of content stored in the CDN cache and for those where multiple files receive relatively similar numbers of requests, such as e-commerce, video game industry, and VoD streaming.
+
+## How does the Cache Sharding feature work?
+
+In a system without Cache Sharding, a CDN server only checks *its own* cache for a file request. This is inefficient when there are many servers in one PoP: if a server *without* the file gets a request, it retrieves a file from the origin instead of a neighboring server.
+
+When Cache Sharding is enabled for a CDN resource, CDN servers within one PoP (or data center) are clustered to use each others’ cache with the <a href="https://www.toptal.com/big-data/consistent-hashing#:~:text=according%20to%20Wikipedia).-,Consistent%20Hashing%20is%20a%20distributed%20hashing%20scheme%20that%20operates%20independently,without%20affecting%20the%20overall%20system" target="_blank">consistent hashing algorithm</a>.
+
+Consistent hashing is a method in which data is stored in a hash table using a hash function. The key of each data item is passed through a hash function, which calculates the address in the “hash ring” and determines in which sector of this ring the hash code is. This hash code indicates on which server the data is stored.
+
+**Example**: Assume three CDN servers, A, B, and C, constitute one group. Server A has file X in its cache. When users request X, their request may reach any of the group’s servers (A, B, or C), depending on workload, connectivity, and other factors. If the request hits A, X is served from its cache. 
+
+If the request hits B or C, they calculate a hash code. Based on this, server B or C knows to which server they should send the request in order to serve X from the cache rather than the origin server. Since server A’s cache has the desired file, server B or C will proxy the request, and server A will serve the user file X from its cache.
+
+If the group has no X in its cache, the server that was initially chosen using a consistent hashing algorithm will download file X from the origin and cache it.
+
+If a server fails, it is removed from the group, and the hash will be recalculated to reflect the failed server. Thus, all subsequent requests will be distributed among other servers of the same group. 
+
+<img src="https://assets.gcore.pro/docs/cdn/cdn-resource-options/cache/cache-sharding-share-cache-between-cdn-servers/cache-sharding-scheme.png" alt="" width="80%">
+
+## What are the benefits of using Cache Sharding?
+
+Cache Sharding optimizes content storage and distribution. Here are some of its benefits in more detail:
+
+- **More efficient cache use.** Only one copy of a file is needed for all the data center’s servers. This means that each CDN server is used efficiently, rather than being occupied with repeats. 
+- **Origin is protected from redundant requests.** CDN servers use the hash key to determine if there is content in the group's cache. The origin is only requested if there is no content cached by the group. This reduces the costs that are incurred when paying for traffic from the CDN servers to the origin. It also lowers the load on the origin server.
+- **Improved content delivery speed.** Checking the caches of nearby servers in a group for a file is quicker than routing a request to the origin. This process enhances the “time to first byte” (TTFB,) indicating a more efficient system.
+
+## How to enable the Cache Sharding feature
+
+<a href="https://gcore.com/docs/cdn/getting-started/create-a-cdn-resource/create-a-cdn-resource-for-only-static-files" target="_blank">Newly created CDN resources</a> have Cache Sharding enabled automatically. If you’re a long-term user unsure whether the feature is activated, please contact our [support team](mailto:support@gcore.com) to request activation.

documentation/cdn/cdn-resource-options/determine-in-which-regions-the-content-will-be-delivered-with-geo-balancer-for-paid-tariffs.md

@@ -1,18 +1,18 @@
 ---
 title: determine-in-which-regions-the-content-will-be-delivered-with-geo-balancer-for-paid-tariffs
-displayName: Geo Balancer (for paid tariffs)
+displayName: Geobalancer (for paid tariffs)
 published: true
 order: 140
 toc:
    --1--Enable or disable the option: "how-to-enable-or-disable-the-option"
-pageTitle: Guidance on Geo Balancer for CDN Use | Gcore
-pageDescription: A helpful guide on determining regional content delivery using the Geo Balancer feature in a paid CDN tariff.
+pageTitle: Guidance on Geobalancer for CDN Use | Gcore
+pageDescription: A helpful guide on determining regional content delivery using the Geobalancer feature in a paid CDN tariff.
 ---
-# Determine in which regions the content will be delivered with geo balancer for paid tariffs
+# Determine in which regions the content will be delivered with Geobalancer for paid tariffs
 
 **Note**: The option is not available for the Free tariff.
 
-Geo Balancer option disables content distribution in certain regions. It can increase the Cache Hit Ratio if your primary audience is located in one, two, or maybe three regions.
+Geobalancer option disables content distribution in certain regions. It can increase the Cache Hit Ratio if your primary audience is located in one, two, or maybe three regions.
 
 Regions for managing:
 - North America

documentation/cdn/troubleshooting/content-delivery-speed-is-low-how-to-solve-the-issue.md

@@ -56,7 +56,7 @@ test.jpg 100%[=================================================>\] 290 --.-KB/s
 ## CDN-resource's settings checking 
 
 1\. Make sure that you don’t use a VPN or proxy.   
-VPN affects the CDN Geo-balancing and you may receive content from a not optimal edge with lower speed. 
+VPN affects the CDN Geobalancing and you may receive content from a not optimal edge with lower speed. 
 
 2\. Make sure that content is being cached. The cache rate is presented by <a href="https://gcore.com/docs/cdn/view-statistics-of-a-cdn-resource" target="_blank">Cache Hit Ratio report</a>. If you noticed that the cache rate is low, use our <a href="https://gcore.com/docs/cdn/troubleshooting/cache-percentage-is-low-how-to-solve-the-issue" target="_blank">instructions</a> to analyze and solve this issue.  
 

documentation/cloud.md

@@ -22,7 +22,7 @@ From the left–side menu, you can access in–depth documentation about Cloud:
 - **Secrets Manager** – management of PKCS12 files for load balancers with HTTP listeners
 - **AI Infrastructure** – overview of Gcore AI infrastructure, AI clusters, virtual vPODs
 - **Function as a Service** – features of Gcore FaaS
-- **Logging as a Service** – overview, configuration, installation of log shippers
+- **Managed Logging** – overview, configuration, installation of log shippers
 - **Terraform** – Cloud management via Terraform
 - **Billing** – charges and invoicing
 

documentation/cloud/about-function-as-a-service.md

@@ -16,7 +16,7 @@ pageDescription: Learn about Function-as-a-Service (FaaS) and its benefits. Expl
 
 ## What is FaaS?
 
-FaaS (Function-as-a-Service) is a cloud service that lets users run code without dealing with the underlying infrastructure. A FaaS provider saves the code to their cloud resources and runs it when requested.
+Function-as-a-Service (FaaS) is a cloud service that lets users run code without dealing with the underlying infrastructure. A FaaS provider saves the code to their cloud resources and runs it when requested.
 
 FaaS is based on serverless computing, in which you can use computing resources such as CPU and memory without actually renting servers on a cloud. You don’t have to choose an operating system, configure networking, patch dependencies, or scale capacity up and down. The necessary number of resources is allocated to you automatically as they are needed.
 

documentation/cloud/kubernetes/bare-metal-kubernetes.md

@@ -13,7 +13,7 @@ pageDescription: Unlock the power of Bare Metal Kubernetes and deploy nodes dire
 ---
 # Bare Metal Kubernetes
 
-With managed Kubernetes-as-a-service, users can deploy worker nodes of their Kubernetes cluster directly on bare metal servers. This empowers users to leverage the full potential of Kubernetes while enjoying the substantial benefits of dedicated hardware resources.
+With Managed Kubernetes, users can deploy worker nodes of their Kubernetes cluster directly on bare metal servers. This empowers users to leverage the full potential of Kubernetes while enjoying the substantial benefits of dedicated hardware resources.
 
 ## How does it work?
 

documentation/cloud/logging-as-a-service/about-logging-as-a-service.md

@@ -12,11 +12,11 @@ toc:
 pageTitle: Logging as a service| Gcore
 pageDescription: Discover Logging for both VMs and bare metal servers. Troubleshoot errors, analyze security incidents and other data using OpenSearch Dashboards.
 ---
-# About Logging as a service
+# About Managed Logging as a service
 
-## What is Logging?  
+## What is Managed Logging?  
 
-Logging, also known as LaaS (logging-as-a-service,) is a service that collects and stores logs from both virtual machines and bare metal servers. Whether you are using Gcore’s infrastructure or your own server, logging can collect logs from any system. You can work with Logging via OpenSearch Dashboards.
+Managed Logging, also known as LaaS (logging-as-a-service,) is a service that collects and stores logs from both virtual machines and bare metal servers. Whether you are using Gcore’s infrastructure or your own server, logging can collect logs from any system. You can work with Logging via OpenSearch Dashboards.
 
 ## How Logging works
 

documentation/cloud/logging-as-a-service/metadata.md

@@ -1,6 +1,6 @@
 ---
 title: metadata
-displayName: Logging as a Service
+displayName: Managed Logging
 published: true
 order: 120
 ---

documentation/ddos-protection/about-ddos-protection.md

@@ -6,6 +6,7 @@ order: 10
 toc:
    --1--How does it work?: "how-does-ddos-protection-work"
    --1--Advanced protection modes: "advanced-protection-modes"
+   --1--DDoS attack statistics: ddos-attack-statistics
    --1--Pricing: "pricing"
 pageTitle: About DDoS Protection | Gcore
 pageDescription: Learn how DDoS Protection safeguards your servers. Explore use cases for different protection modes and select the best option for your needs.
@@ -67,6 +68,14 @@ With an always-on mode, your traffic passes through the TMS, even when there is
    </tr>
 </table>
 
+## DDoS attack statistics
+
+With the real-time DDoS attack statistics feature, you can access a live dashboard that provides a comprehensive overview of ongoing attacks on your protected resources.
+
+You can filter statistics by specific data centers, time intervals, and attack metrics such as bits per second (bps) and packets per second (pps.)
+
+<img src="https://assets.gcore.pro/docs/ddos-protection/ddos-attack-statistics.png" alt="">
+
 ## Pricing
 
  The price for DDoS Protection depends on three factors:

documentation/dns/dns-failover/about-dns-failover.md

@@ -24,7 +24,7 @@ It’s a paid feature that is currently available for free in beta version. If y
 
 DNS Failover is needed to make your site or application available for all users in case some servers are down.
 
-It’s especially important for business areas where the loss of availability means the loss of customers. Let’s use an example to explain. Imagine that you own an online store that works in Europe and the United States. Your site is on two servers: a European one and an American one. You use geo balancing to route people from all over the world to the closest server so that the site loads faster. Customers from Paris, France, and Barcelona, Spain, are balanced to the European server, while users from Vancouver, Canada, and Chicago, United States, are balanced to the American one.
+It’s especially important for business areas where the loss of availability means the loss of customers. Let’s use an example to explain. Imagine that you own an online store that works in Europe and the United States. Your site is on two servers: a European one and an American one. You use Geobalancing to route people from all over the world to the closest server so that the site loads faster. Customers from Paris, France, and Barcelona, Spain, are balanced to the European server, while users from Vancouver, Canada, and Chicago, United States, are balanced to the American one.
 
 <img src="https://assets.gcore.pro/docs/dns/dns-failover/about-dns-failover/9684855295377.png" alt="" width="80%">
 
@@ -42,7 +42,7 @@ When your European server recovers, DNS Failover will detect that and return its
 
 **In common.** DNS Failover sends regular requests toward configured addresses to determine whether they are available. If a server doesn’t respond, DNS Failover will send DNS servers the command to exclude its IP from DNS responses. When the server recovers, DNS Failover will send DNS the command to return its IP to DNS responses.
 
-By default, DNS Failover uses round robin load balancing to distribute users’ requests across available web servers. However, you can enable geo balancing during configuration.
+By default, DNS Failover uses round robin load balancing to distribute users’ requests across available web servers. However, you can enable Geobalancing during configuration.
 
 **In detail:**
 
@@ -68,7 +68,7 @@ If a web server doesn’t send a response to DNS Failover within the set timeout
 
 <img src="https://assets.gcore.pro/docs/dns/dns-failover/about-dns-failover/9684879021841.png" alt="" width="80%">
 
-The balancing mechanism determines which server responds to requests destined for the unavailable server. By default, DNS Failover uses round-robin, but you can configure your own mechanism, such as geo balancing. The configuration for this mechanism is described in the article "<a href="https://gcore.com/docs/dns/dns-failover/configure-and-use-dns-failover" target="_blank">DNS Failover. Configure and use</a>".
+The balancing mechanism determines which server responds to requests destined for the unavailable server. By default, DNS Failover uses round-robin, but you can configure your own mechanism, such as Geobalancing. The configuration for this mechanism is described in the article "<a href="https://gcore.com/docs/dns/dns-failover/configure-and-use-dns-failover" target="_blank">DNS Failover. Configure and use</a>".
 
 5\. DNS Failover keeps sending requests to web servers. When the web server becomes available and responds, the feature will send the appropriate update to the DNS server.
 

documentation/dns/dns-records/manage-dns-records-advanced-interface-mode-with-balancing.md

@@ -19,7 +19,7 @@ toc:
    --1--Edit: "edit-a-dns-record"
    --1--Delete: "delete-a-dns-record"
 pageTitle: Managing DNS records in advanced mode | Gcore
-pageDescription: Learn how to add, edit and delete DNS records in the advanced interface mode with Geo Proximity and Geo balancing.
+pageDescription: Learn how to add, edit and delete DNS records in the advanced interface mode with Geo Proximity and Geobalancing.
 ---
 # Manage DNS records (advanced interface mode with balancing)
 

documentation/hosting/about-gcore-referral-program.md

@@ -4,6 +4,8 @@ displayName: Referral program
 order: 100
 published: true
 toc:
+pageTitle: About Gcore Referral program | Gcore
+pageDescription: Discover the Gcore Referral Program! Earn monetary bonuses by sharing your referral link on websites, forums, or online platforms.
 ---
 # About Gcore Referral program
 

documentation/hosting/become-reseller-and-resell-our-services.md

@@ -4,8 +4,10 @@ displayName: Become a reseller
 order: 90
 published: true
 toc:
+pageTitle: Become a reseller | Gcore
+pageDescription: Learn how to become a Gcore reseller.
 ---
-# Become reseller and resell our services
+# Become a reseller and resell our services
 
 Reselling is a way of a partnership when you purchase our servers and provide them to your customers using your own billing system.
 

documentation/hosting/contact-our-technical-support.md

@@ -6,6 +6,8 @@ order: 70
 toc:
 --1--Chat: "chat"
 --1--Ticket: "ticket"
+pageTitle: Contact our technical support | Gcore
+pageDescription: Learn how to send tickets to the Gcore support team.
 ---
 # Contact our technical support
 

documentation/hosting/manage-hosting-services-via-api.md

@@ -4,6 +4,8 @@ displayName: API
 order: 80
 published: true
 toc:
+pageTitle: Manage Hosting services via API | Gcore
+pageDescription: Discover the links to the Gcore API documentation to manage Hosting services.
 ---
 # Manage Hosting services via API
 

documentation/hosting/other-services/bgp/activate-bgp.md

@@ -3,6 +3,8 @@ title: activate-bgp
 displayName: Activate BGP
 published: true
 toc:
+pageTitle: Activate BGP | Gcore
+pageDescription: Learn how to activate BGP for enhanced IP-address announcements, getting connected in China, or reselling. 
 ---
 # Activate BGP
 

documentation/hosting/other-services/ddos-protection/about-gcore-ddos-protection-for-dedicated-servers.md

@@ -7,6 +7,8 @@ toc:
    --1--How it works: "how-it-works"
    --1--Advanced protection modes: "advanced-protection-modes"
    --1--Billing: "billing"
+pageTitle: DDoS Protection for dedicated servers | Gcore
+pageDescription: Discover GCore DDoS Protection for dedicated servers. Choose between Basic (free) and Advanced (paid) Protection.
 ---
 # About GCore DDoS Protection for dedicated servers
 

documentation/hosting/other-services/ddos-protection/activate-ddos-protection-for-your-dedicated-servers.md

@@ -4,6 +4,8 @@ displayName: Activate
 order: 20
 published: true
 toc:
+pageTitle: Activate DDoS Protection | Gcore
+pageDescription: Learn how to activate Advanced DDoS Protection for dedicated servers.
 ---
 # Activate DDoS Protection for your dedicated servers
 

documentation/hosting/other-services/link-aggreagtion/activate-link-aggregation.md

@@ -5,6 +5,8 @@ published: true
 toc:
  --1--Setup example for Ubuntu 14.04: "setup-example-for-ubuntu-14-04"
  --1--Configure LACP on the server: "configure-lasp-on-the-server"
+pageTitle: Activate Link Aggregation | Gcore
+pageDescription: Learn how to activate Link Aggregation (LACP) to boost server performance and enhance fault tolerance.
 ---
 # Activate Link Aggregation
 

documentation/hosting/other-services/ssl-certificates/about-ssl-certificates.md

@@ -6,6 +6,8 @@ published: true
 toc:
    --1--Domain Validated Certificate (DV): "domain-validated-certificate-dv"
    --1--Company Validated Certificate (OV): "company-validated-certificate-ov"
+pageTitle: About SSL certificates | Gcore
+pageDescription: Learn about SSL certificates, which provide essential security by encrypting communications between your website and users.
 ---
 # About SSL certificates
 

documentation/hosting/other-services/ssl-certificates/activate-an-ssl-certificate.md

@@ -6,6 +6,8 @@ published: true
 toc:
     --1--DV certificates: "dv-certificates"
     --1--OV certificates: "ov-certificates"
+pageTitle: Activate an SSL certificate | Gcore
+pageDescription: Learn how to activate a DV or an OV SSL certificate.
 ---
 # Activate an SSL certificate
 

documentation/hosting/other-services/ssl-certificates/order-an-ssl-certificate.md

@@ -10,6 +10,8 @@ toc:
     --1--Generating a key: "generating-a-key"
     --1--Enter the contact information: "enter-the-contact-information"
     --1--Confirm domain ownership: "confirm-domain-ownership"
+pageTitle: Activate an SSL certificate | Gcore
+pageDescription: Learn how to buy an SSL certificate.
 ---
 # Order an SSL certificate
 

documentation/hosting/payments/check-the-payment-history.md

@@ -4,6 +4,8 @@ displayName: Payment history
 published: true
 order: 50
 toc:
+pageTitle: Check the payment history | Gcore
+pageDescription: Learn how to check the history of payments for your account.
 ---
 # Check the payment history
 

documentation/hosting/payments/pay-for-gcore-services-payment-methods.md

@@ -7,6 +7,8 @@ toc:
    --1--Via PayPal: "pay-via-paypal"
    --1--Via bank transfer: "pay-via-bank-transfer"
    --1--Via bank card or Alipay: "pay-via-bank-card-or-alipay"
+pageTitle: Pay for Gcore services | Gcore
+pageDescription: Learn about payment methods for Gcore services.
 ---
 # Pay for Gcore services (payment methods)