diff --git a/src/content/docs/en/pages/architectures/api-gateways/api-gateways-security.mdx b/src/content/docs/en/pages/architectures/api-gateways/api-gateways-security.mdx index d4b12f01dd..ce237ea191 100644 --- a/src/content/docs/en/pages/architectures/api-gateways/api-gateways-security.mdx +++ b/src/content/docs/en/pages/architectures/api-gateways/api-gateways-security.mdx @@ -51,7 +51,7 @@ Through this perimeter, you can implement solutions such as: - [DDoS Protection](/en/documentation/products/secure/edge-firewall/ddos-protection/): detects and mitigates DDoS and DoS attacks. - [Network Shield](/en/documentation/products/secure/edge-firewall/network-layer-protection/): allows you to create lists with IP addresses or countries with suspicious behavior and restrict their access. - [Functions for Firewall](/en/documentation/products/secure/edge-firewall/edge-functions/): build event-driven, serverless applications including functions with your own security source code. -- [Marketplace Integrations](/en/documentation/products/marketplace/integrations/): edge function-based functionalities to compose and improve your applications, enforcing security policies. +- [Marketplace Integrations](/en/documentation/products/marketplace/integrations/): function-based functionalities to compose and improve your applications, enforcing security policies. - [Data Stream](/en/documentation/products/observe/data-stream/) and [Real-Time Events](/en/documentation/products/observe/real-time-events/) enable you to monitor all API Gateway activity. --- diff --git a/src/content/docs/en/pages/architectures/edge-enhanced/edge-enhanced.mdx b/src/content/docs/en/pages/architectures/edge-enhanced/edge-enhanced.mdx index 023cd942f0..cab0033ec0 100644 --- a/src/content/docs/en/pages/architectures/edge-enhanced/edge-enhanced.mdx +++ b/src/content/docs/en/pages/architectures/edge-enhanced/edge-enhanced.mdx @@ -46,7 +46,7 @@ After this process, the application returns a response to the request. - On [Console](https://console.azion.com), create an application using the **+ Create** button on the homepage. - Using the [Azion API](https://api.azion.com/#d43c5509-fb99-4b20-a7bd-64f0924af352) to create an application. - Using the [Azion CLI](/en/documentation/devtools/cli/create/#edge-applications) to create and deploy an application. -2. [Create an edge function](/en/documentation/products/build/edge-application/edge-functions/#implementation) and [instantiate](/en/documentation/products/guides/build/instantiate-edge-functions/) it in the recently created application. +2. [Create an function](/en/documentation/products/build/edge-application/edge-functions/#implementation) and [instantiate](/en/documentation/products/guides/build/instantiate-edge-functions/) it in the recently created application. 3. Create a domain and associate it with the application: - On Console, [create a domain](/en/documentation/products/guides/configure-a-domain/) using the + Create button on the homepage. - Using the [Azion API](https://api.azion.com/#d43c5509-fb99-4b20-a7bd-64f0924af352) to create a domain. diff --git a/src/content/docs/en/pages/architectures/edge-firewall/online-fraud-prevention.mdx b/src/content/docs/en/pages/architectures/edge-firewall/online-fraud-prevention.mdx index 4837104bbe..e15d17b66d 100644 --- a/src/content/docs/en/pages/architectures/edge-firewall/online-fraud-prevention.mdx +++ b/src/content/docs/en/pages/architectures/edge-firewall/online-fraud-prevention.mdx @@ -5,7 +5,7 @@ description: >- permalink: >- /documentation/architectures/edge-firewall/online-fraud-prevention/ meta_tags: >- - Fraud prevention, Zero-Trust Security, threat intelligence, Account Takeover, credential stuffing, phishing, Synthetic Identity Fraud, cyber security, Bot management, Edge Firewall, online security, e-commerce, fintech + Fraud prevention, Zero-Trust Security, threat intelligence, Account Takeover, credential stuffing, phishing, Synthetic Identity Fraud, cyber security, Bot management, Firewall, online security, e-commerce, fintech namespace: docs_arch_online_fraud_prevention --- diff --git a/src/content/docs/en/pages/architectures/security-automation/security-automation.mdx b/src/content/docs/en/pages/architectures/security-automation/security-automation.mdx index 68c86477b1..bbfe4c6bb7 100644 --- a/src/content/docs/en/pages/architectures/security-automation/security-automation.mdx +++ b/src/content/docs/en/pages/architectures/security-automation/security-automation.mdx @@ -56,7 +56,7 @@ In this context, autonomous systems operate with minimal or no human interventio ## Implementation -1. Create an [edge application](/en/documentation/products/guides/build/build-an-application/). +1. Create an [application](/en/documentation/products/guides/build/build-an-application/). 2. Configure a [firewall](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/). 3. Define all your rules and configurations: - [Rules Engine rules](/en/documentation/products/secure/edge-firewall/rules-engine/), using criteria and behaviors to define how the request is handled. It includes rules related to network lists, WAF Rules, Custom Allowed Rules, rate limits, custom responses, blocking and dropping requests, and run functions. diff --git a/src/content/docs/en/pages/architectures/security-modernization/security-modernization-with-edge-computing.mdx b/src/content/docs/en/pages/architectures/security-modernization/security-modernization-with-edge-computing.mdx index b7504fb6ca..fe5ba35416 100644 --- a/src/content/docs/en/pages/architectures/security-modernization/security-modernization-with-edge-computing.mdx +++ b/src/content/docs/en/pages/architectures/security-modernization/security-modernization-with-edge-computing.mdx @@ -72,7 +72,7 @@ This use case is ideal for organizations looking to build a strong online presen 3. [Create a WAF rule set](/en/documentation/products/guides/secure/create-waf-rule-set/), configuring Threat Type and Sensitivity levels. 4. [Create a network list](/en/documentation/products/guides/blocklists-ip-addresses-edge/) in Network Shield. 5. [Create your security functions](/en/documentation/products/guides/edge-functions/firewall/) or explore marketplace security integrations like [reCaptcha](/en/documentation/products/guides/recaptcha/), [hCaptcha](/en/documentation/products/guides/hcaptcha/), [Secure Token](/en/documentation/products/guides/secure-token/), [JWT](/en/documentation/products/guides/jwt/), and [much more](/en/documentation/products/guides/#marketplace). -6. [Create rules in Rules Engine](/en/documentation/products/guides/secure/work-with-rules-engine/) for Firewall to define the behavior to be executed when the Firewall detects a request matching the criteria defined by the rule sets, network lists, and edge functions. +6. [Create rules in Rules Engine](/en/documentation/products/guides/secure/work-with-rules-engine/) for Firewall to define the behavior to be executed when the Firewall detects a request matching the criteria defined by the rule sets, network lists, and functions. 7. Use [Observe products](/en/documentation/products/observe/overview/) to monitor your requests and traffic. --- diff --git a/src/content/docs/en/pages/build-journey/troubleshooting/debug-apps.mdx b/src/content/docs/en/pages/build-journey/troubleshooting/debug-apps.mdx index 5ed13d7c5d..b3583644b1 100644 --- a/src/content/docs/en/pages/build-journey/troubleshooting/debug-apps.mdx +++ b/src/content/docs/en/pages/build-journey/troubleshooting/debug-apps.mdx @@ -13,7 +13,7 @@ namespace: docs_build_debug_apps import LinkButton from 'azion-webkit/linkbutton' -The debugging process allows checking if the rules, messages, and variables you've created are working properly. When you constantly debug an application or an edge function, you improve your monitoring process and you're able to identify errors and then fix them. +The debugging process allows checking if the rules, messages, and variables you've created are working properly. When you constantly debug an application or an function, you improve your monitoring process and you're able to identify errors and then fix them. ## Applications diff --git a/src/content/docs/en/pages/devtools/api-graphql/features/consumption-fields.mdx b/src/content/docs/en/pages/devtools/api-graphql/features/consumption-fields.mdx index 1d75a57147..b56bef7540 100644 --- a/src/content/docs/en/pages/devtools/api-graphql/features/consumption-fields.mdx +++ b/src/content/docs/en/pages/devtools/api-graphql/features/consumption-fields.mdx @@ -40,7 +40,7 @@ If you're logged in with a group or reseller account, you can query the consumpt |---------------|-------------|---------------|-------------| | [Data Stream](/en/documentation/products/guides/query-data-stream-usage-data-with-graphql/) | 1498670028 | - | - `data_streamed`: total volume of data streamed through Data Stream.
- `requests`: total number of requests processed by Data Stream. | | [Applications](/en/documentation/products/guides/query-edge-application-usage-data-with-graphql/) | 1441740010 | - image_processor
- edge_firewall
- load_balancer
- application_accelerator | - `data_transferred_total`: total amount of data transferred through Applications.
- `requests`: total number of requests received by Application.
- `waf_requests`: total number of requests inspected by WAF. | -| [Functions](/en/documentation/products/guides/query-edge-functions-usage-data-with-graphql/) | 1531930033 | - | - `compute_time`: Total execution time (in milliseconds) of Functions in milliseconds.
- `invocations`: total number of times an edge function was executed. | +| [Functions](/en/documentation/products/guides/query-edge-functions-usage-data-with-graphql/) | 1531930033 | - | - `compute_time`: Total execution time (in milliseconds) of Functions in milliseconds.
- `invocations`: total number of times an function was executed. | | [Image Processor](/en/documentation/products/guides/query-image-processor-usage-data-with-graphql/) | 1441110021 | - | `images_processed`: total number of images processed by Image Processor. | | [Cache](/en/documentation/products/guides/query-tiered-cache-usage-data-with-graphql/) | 1564082375 | - | - `data_transferred_total`: total amount of data transferred through Tiered Cache.
- `requests`: total number of cache requests processed by Tiered Cache. | diff --git a/src/content/docs/en/pages/devtools/api-graphql/features/events-fields.mdx b/src/content/docs/en/pages/devtools/api-graphql/features/events-fields.mdx index b9a450e836..582e375e67 100644 --- a/src/content/docs/en/pages/devtools/api-graphql/features/events-fields.mdx +++ b/src/content/docs/en/pages/devtools/api-graphql/features/events-fields.mdx @@ -7,7 +7,7 @@ permalink: /documentation/devtools/graphql-api/features/gql-real-time-events-fie meta_tags: >- GraphQL API, Azion Console, Real-Time Events, dataset fields, account management, API data querying, application, data stream, HTTP events, - edge functions + functions namespace: documentation_graphql_events_fields menu_namespace: graphqlMenu --- @@ -76,10 +76,10 @@ See each available field and their descriptions below. | Field | Description | | ----- | ----------- | | configurationId | Unique Azion configuration identifier set on virtual host configuration file. Example: `1595368520` | -| edgeFunctionsInstanceIdList | List of edge functions instances that were invoked during the request. Example: `10728` | +| edgeFunctionsInstanceIdList | List of functions instances that were invoked during the request. Example: `10728` | | edgeFunctionsInitiatorTypeList | List of initiators used in the function separated by `;`. Can be `1` (Applications) or `2` (Firewall). | -| edgeFunctionsList | List of edge functions that were invocated during the request, in order. The order begins from left to right, meaning functions on the left were invocated first. Example: `3324;43` | -| edgeFunctionsSolutionId | Identifier of your edge function. Example: `1321` | +| edgeFunctionsList | List of functions that were invocated during the request, in order. The order begins from left to right, meaning functions on the left were invocated first. Example: `3324;43` | +| edgeFunctionsSolutionId | Identifier of your function. Example: `1321` | | edgeFunctionsTime | Total execution time, in seconds, for the function during its processing. This field is the result of a sum. Example: `0.021` | | functionLanguage | Language used in the function. Example: `javascript` | | ts | Timestamp of when the event was created. Example: `2022-10-20T10:10:10` | @@ -120,7 +120,7 @@ See each available field and their descriptions below. | sslProtocol | Protocol for an established TLS connection. Example: `TLS v1.2` | | sslServerName | Returns the session identifier of an established SSL connection. Example: `mywebsite.com` | | sslSessionReused | Returns `r` if an SSL session was reused or `.` if it wasn't. | -| stacktrace | Provides the names of the Rules Engine from your edge application or your firewall that are run by the request. Example: `{\\\"edge_firewall\\\":[\\\"Global - Set WAF\\\"]}` | +| stacktrace | Provides the names of the Rules Engine from your application or your firewall that are run by the request. Example: `{\\\"edge_firewall\\\":[\\\"Global - Set WAF\\\"]}` | | status | HTTP status code of the request. Example: `200` | | streamName | ID set through virtual host configuration based on location directive. Set on virtual host configuration file. Example: `company_sector.sdp` | | tcpinfoRtt | Round-Trip Time (RTT) in microseconds measured by the edge for the user. Available on systems that support the TCP_INFO socket option. Example: `72052` | diff --git a/src/content/docs/en/pages/devtools/api-graphql/features/metrics-fields.mdx b/src/content/docs/en/pages/devtools/api-graphql/features/metrics-fields.mdx index 96256938c6..97da1b9e34 100644 --- a/src/content/docs/en/pages/devtools/api-graphql/features/metrics-fields.mdx +++ b/src/content/docs/en/pages/devtools/api-graphql/features/metrics-fields.mdx @@ -179,7 +179,7 @@ When a field is a result of any kind of calculation, such as a sum, they're cons | configurationId | Unique Azion configuration identifier set on virtual host configuration file. Example: `1595368520` | | edgeFunctionId | Identification of your Function. Example: `1321` | | edgeFunctionInstanceId | Identification of your Function Instance. Example: `10590` | -| edgeFunctionsInstanceIdList | List of edge functions instances that were invocated during the request. Example: `10728` | +| edgeFunctionsInstanceIdList | List of functions instances that were invocated during the request. Example: `10728` | | functionLanguage | Language used in the function. Example: `javascript` | | initiatorType | Initiator used in the function. Can be `1` (Applications) or `2` (Firewall). | | invocations | Total amount of an invocation. This field is the result of a sum. Example: `8` | @@ -192,7 +192,7 @@ When a field is a result of any kind of calculation, such as a sum, they're cons | Calculated field | Description | | ---------------- | ----------- | -| edgeApplicationInvocations | Total amount of invocations of a function from an edge application. Example: `50` | +| edgeApplicationInvocations | Total amount of invocations of a function from an application. Example: `50` | | edgeFirewallInvocations | Total amount of invocations of a function from a firewall. Example: `30` | --- diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/code-editor/code-editor.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/code-editor/code-editor.mdx index f9eac6986d..d6f3606319 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/code-editor/code-editor.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/code-editor/code-editor.mdx @@ -13,7 +13,7 @@ namespace: documentation_products_edge_functions_runtime_code_editor menu_namespace: runtimeMenu --- -The new code editor for [Functions](/en/documentation/products/build/edge-application/edge-functions/) is the best way to get started developing your edge functions on the Azion platform. It's a web-based code editor that makes it easier and more intuitive to develop at the edge of the network. It's empowered by the [Monaco Code Editor](https://microsoft.github.io/monaco-editor/docs.html), used in [VS Code](https://code.visualstudio.com/), so if you're used to VS Code, you'll get familiar with it right away. The Monaco Code Editor main features available for the **Functions Code Editor** are: +The new code editor for [Functions](/en/documentation/products/build/edge-application/edge-functions/) is the best way to get started developing your functions on the Azion platform. It's a web-based code editor that makes it easier and more intuitive to develop at the edge of the network. It's empowered by the [Monaco Code Editor](https://microsoft.github.io/monaco-editor/docs.html), used in [VS Code](https://code.visualstudio.com/), so if you're used to VS Code, you'll get familiar with it right away. The Monaco Code Editor main features available for the **Functions Code Editor** are: - Syntax Highlighting - IntelliSense diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/node-polyfills/cells-node.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/node-polyfills/cells-node.mdx index 121e66815f..349d3f38be 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/node-polyfills/cells-node.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/node-polyfills/cells-node.mdx @@ -15,7 +15,7 @@ import LinkButton from 'azion-webkit/linkbutton' ## Node.js APIs supported in Azion Runtime -The compatibility between **Azion Runtime** and **Node.js** is an ongoing task, but a set of Node Runtime APIs are listed and compatible with Azion Runtime. The following list of APIs can be imported inside edge functions with the standard import syntax: +The compatibility between **Azion Runtime** and **Node.js** is an ongoing task, but a set of Node Runtime APIs are listed and compatible with Azion Runtime. The following list of APIs can be imported inside functions with the standard import syntax: ```js import { API } from "import-origin"; @@ -31,7 +31,7 @@ import { API } from "import-origin"; ### File System (FS) module support -The Azion Runtime provides native support for the File System (FS) module, allowing you to interact with the file system within your edge functions. +The Azion Runtime provides native support for the File System (FS) module, allowing you to interact with the file system within your functions. Async: diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/use-polyfills.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/use-polyfills.mdx index 8aedc7fe2c..7caf26b6d5 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/use-polyfills.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/use-polyfills.mdx @@ -72,7 +72,7 @@ You can start typing the template's name to filter the results. ```sh ? Choose a template: [Use arrows to move, type to filter] - Azion Edge SQL + Azion SQL Database Drizzle + Neon Sample Drizzle + TiDB Sample Drizzle + Turso Sample diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/overview/overview.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/overview/overview.mdx index 6d7bbef092..b0993bd51c 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/overview/overview.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/overview/overview.mdx @@ -2,10 +2,10 @@ title: Azion Runtime description: >- The Azion Runtime is a set of tools for developing applications at the Edge. - The Azion Runtime allows you to write JavaScript edge functions built on Web + The Azion Runtime allows you to write JavaScript functions built on Web standards. Edge functions help you to implement the business logic and create serverless applications, at the edge of the network, closer to users. -meta_tags: 'edge function, edge computing, serverless, jamstack' +meta_tags: 'function, edge computing, serverless, jamstack' namespace: documentation_products_edge_functions_runtime_overview permalink: /documentation/runtime/overview/ menu_namespace: runtimeMenu diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/encoding/2021-01-14-index.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/encoding/2021-01-14-index.mdx index 0e91af00b8..bd54368131 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/encoding/2021-01-14-index.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/encoding/2021-01-14-index.mdx @@ -1,7 +1,7 @@ --- title: JavaScript Runtime APIs - Encoding description: Encoding -meta_tags: 'encoding, runtime api, edge functions' +meta_tags: 'encoding, runtime api, functions' namespace: documentation_products_edge_functions_runtime_apis_javascript_encoding permalink: >- /documentation/products/applications/functions/runtime-apis/javascript/encoding/ diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/index.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/index.mdx index 269132aa59..74ceb8ff73 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/index.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/index.mdx @@ -9,7 +9,7 @@ permalink: /documentation/runtime-apis/javascript/ menu_namespace: runtimeMenu --- -The **JavaScript Runtime Environment** is a set of APIs that are available as tools for the development of edge functions. +The **JavaScript Runtime Environment** is a set of APIs that are available as tools for the development of functions. You can deploy projects using the Azion Edge Infrastructure, and automatically provision what is needed for your code to run on a low latency rate, closer to the users. diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/request/2021-01-14-index.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/request/2021-01-14-index.mdx index 7806c6f54e..3a52fdbd95 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/request/2021-01-14-index.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/request/2021-01-14-index.mdx @@ -12,7 +12,7 @@ The `Request` interface represents an HTTP request and integrates the [Fetch API ## How it works -The Request object can be built and also seen as the property of a [fetchevent](/en/documentation/products/edge-application/edge-functions/runtime-apis/javascript/fetch-event/) received by edge function. +The Request object can be built and also seen as the property of a [fetchevent](/en/documentation/products/edge-application/edge-functions/runtime-apis/javascript/fetch-event/) received by function. ```js addEventListener("fetch", event => { diff --git a/src/content/docs/en/pages/devtools/cli/azion-cli/commands/delete/delete.mdx b/src/content/docs/en/pages/devtools/cli/azion-cli/commands/delete/delete.mdx index 984eae28b4..4778b8db09 100644 --- a/src/content/docs/en/pages/devtools/cli/azion-cli/commands/delete/delete.mdx +++ b/src/content/docs/en/pages/devtools/cli/azion-cli/commands/delete/delete.mdx @@ -5,7 +5,7 @@ description: >- applications, functions, and setting up cache rules effectively. permalink: /documentation/devtools/cli/delete/ meta_tags: >- - azion CLI, application deletion, edge function removal, cache settings + azion CLI, application deletion, function removal, cache settings management, rules engine configuration, domain handling, object storage solutions namespace: documentation_cli_delete @@ -69,7 +69,7 @@ azion delete edge-function --function-id ##### function-id -The `--function-id` flag is the unique identifier of the edge function. +The `--function-id` flag is the unique identifier of the function. #### Optional flags diff --git a/src/content/docs/en/pages/devtools/cli/azion-cli/commands/describe/describe.mdx b/src/content/docs/en/pages/devtools/cli/azion-cli/commands/describe/describe.mdx index 6ba07ab275..6872dd3dbe 100644 --- a/src/content/docs/en/pages/devtools/cli/azion-cli/commands/describe/describe.mdx +++ b/src/content/docs/en/pages/devtools/cli/azion-cli/commands/describe/describe.mdx @@ -5,7 +5,7 @@ description: >- domains, and more with Azion CLI. permalink: /documentation/devtools/cli/describe/ meta_tags: >- - azion, CLI, applications, edge functions, rules engine, cache settings, + azion, CLI, applications, functions, rules engine, cache settings, domains, origins, variables, object storage, command usage, resource management namespace: documentation_cli_describe menu_namespace: cliMenuAlpha @@ -78,7 +78,7 @@ azion describe edge-function --function-id ##### function-id -The `--function-id` flag is the unique identifier of the edge function. +The `--function-id` flag is the unique identifier of the function. #### Optional flags @@ -92,7 +92,7 @@ The `--out` flag exports the output to the given ``. ##### with-code -The `--with-code` flag displays the edge function's code; disabled by default. +The `--with-code` flag displays the function's code; disabled by default. ##### help @@ -277,7 +277,7 @@ The `--help` option displays more information about the `azion describe variable --- -## Edge Storage object +## Object Storage object #### Usage diff --git a/src/content/docs/en/pages/devtools/cli/azion-cli/commands/dev-command/dev.mdx b/src/content/docs/en/pages/devtools/cli/azion-cli/commands/dev-command/dev.mdx index 98c7e92084..e5b89ceaf5 100644 --- a/src/content/docs/en/pages/devtools/cli/azion-cli/commands/dev-command/dev.mdx +++ b/src/content/docs/en/pages/devtools/cli/azion-cli/commands/dev-command/dev.mdx @@ -42,7 +42,7 @@ azion dev Once you've initialized the local development server, the application goes through the `build` process. ```sh -Building your Edge Application. This process may take a few minutes +Building your Applications. This process may take a few minutes Running build step command: ... ``` diff --git a/src/content/docs/en/pages/devtools/cli/azion-cli/commands/list/list.mdx b/src/content/docs/en/pages/devtools/cli/azion-cli/commands/list/list.mdx index 14bb24639c..5a1d276b69 100644 --- a/src/content/docs/en/pages/devtools/cli/azion-cli/commands/list/list.mdx +++ b/src/content/docs/en/pages/devtools/cli/azion-cli/commands/list/list.mdx @@ -1,7 +1,7 @@ --- title: Azion CLI list description: >- - List your applications, edge functions and other resources through Azion + List your applications, functions and other resources through Azion CLI. meta_tags: 'cli, edge, list, development' namespace: documentation_cli_list diff --git a/src/content/docs/en/pages/devtools/mcp/mcp-examples.mdx b/src/content/docs/en/pages/devtools/mcp/mcp-examples.mdx index 9020f814cc..eb5a02cb77 100644 --- a/src/content/docs/en/pages/devtools/mcp/mcp-examples.mdx +++ b/src/content/docs/en/pages/devtools/mcp/mcp-examples.mdx @@ -220,7 +220,7 @@ Get instant answers about Azion Platform features and capabilities. |-------|-----------|--------| | "How do I configure DDoS protection?" | `search_azion_docs_and_site` | DDoS Protection setup guide | | "Show me Next.js deployment examples" | `search_azion_code_samples` | Next.js templates and samples | -| "What CLI commands manage edge functions?" | `search_azion_cli_commands` | Functions-related CLI commands | +| "What CLI commands manage functions?" | `search_azion_cli_commands` | Functions-related CLI commands | | "How to create Terraform resources?" | `search_azion_terraform` | Terraform provider examples | --- diff --git a/src/content/docs/en/pages/guides/debug-rules/debug-rules.mdx b/src/content/docs/en/pages/guides/debug-rules/debug-rules.mdx index 3bab12fbdb..0a02814baf 100644 --- a/src/content/docs/en/pages/guides/debug-rules/debug-rules.mdx +++ b/src/content/docs/en/pages/guides/debug-rules/debug-rules.mdx @@ -16,7 +16,7 @@ import Tabs from '~/components/tabs/Tabs' -**Debug Rules** allows you to check whether rules or rule sets created using the **Rules Engine** module for **Edge Application** and **Firewall** have been successfully executed in your application. +**Debug Rules** allows you to check whether rules or rule sets created using the **Rules Engine** module for **Applications** and **Firewall** have been successfully executed in your application. You can debug rules using the **GraphQL API**, Azion **Data Stream**, and Azion **Real-Time Events**. @@ -110,7 +110,7 @@ Send your request. You’ll receive a response similar to this: } ``` -In this example, the **GraphQL API** has returned all active request and response phase rules created for **Edge Application**, as well as an active **Firewall** rule set. +In this example, the **GraphQL API** has returned all active request and response phase rules created for **Applications**, as well as an active **Firewall** rule set. For more information on the **GraphQL API**, visit the [datasets documentation page](/en/documentation/devtools/graphql-api/features/#datasets). @@ -171,7 +171,7 @@ To see all your created stream, go to the **Data Stream** page on Azion Console | Variable | Definition | | --- | --- | | $time | Request date and time. Example: Oct. 31st, 2022 - 19:30:41 | -| $traceback | Provides the names of the rules created using Rules Engine for Edge Application and Firewall that are run by the request. | +| $traceback | Provides the names of the rules created using Rules Engine for Applications and Firewall that are run by the request. | :::note The `Set WAF [Your WAF]` Firewall behavior performs special processing, allowing other rules to be processed simultaneously. As a result, logs may display other rules in the `traceback` field, even if the WAF Rule Set is configured to block and return the request. However, the WAF rules operate correctly, blocking requests that match the specified criteria. This behavior is standard for the platform. @@ -201,7 +201,7 @@ The **traceback** field should contain the type of rule executed and the behavio {\"edge_application_response\":[\"Add Azion Cookie\"],\"edge_firewall\":[\"Set WAF\",\"Rate-Limit Root\"],\"edge_application_request\":[\"Default Rule\",\"Test Send Cert to Origin 1\",\"Test Send Cert to Origin 2\"]} ``` -In this example, the **traceback** field contains all active request and response phase rules created for **Edge Application**, as well as an active **Firewall** rule set. +In this example, the **traceback** field contains all active request and response phase rules created for **Applications**, as well as an active **Firewall** rule set. :::note The `Set WAF [Your WAF]` Firewall behavior performs special processing, allowing other rules to be processed simultaneously. As a result, logs may display other rules in the `traceback` field, even if the WAF Rule Set is configured to block and return the request. However, the WAF rules operate correctly, blocking requests that match the specified criteria. This behavior is standard for the platform. diff --git a/src/content/docs/en/pages/guides/devtools/customize-console-ui/index.mdx b/src/content/docs/en/pages/guides/devtools/customize-console-ui/index.mdx index 6cfbcf6f98..6908143fd3 100644 --- a/src/content/docs/en/pages/guides/devtools/customize-console-ui/index.mdx +++ b/src/content/docs/en/pages/guides/devtools/customize-console-ui/index.mdx @@ -90,7 +90,7 @@ You can use this function with the routes defined in the `src/router/routes` fol > Domain - and select an edge application to launch online. + and select an application to launch online.