Skip to content

Commit a6217c1

Browse files
committed
Proofreading
1 parent a6dc4bc commit a6217c1

5 files changed

Lines changed: 5 additions & 5 deletions

File tree

content/en/docs/deployment/private-cloud/private-cloud-deploy/_index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ All environments are defined as production environments, which means that [secur
130130

131131
8. Click **Next**.
132132

133-
{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/configureEnvResources.png" class="no-border" >}}
133+
{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/configure-env-resources.png" class="no-border" >}}
134134

135135
9. Select **Core Resources**.
136136

@@ -529,7 +529,7 @@ For a *connected* cluster, the top level MendixApp CRD will be deleted from the
529529

530530
* The database will be dropped and the database user will be deleted from the database server — databases and users from other environments will remain untouched.
531531

532-
{{% alert color="info" %}}If the storage plan is using a JDBC plan (not Postgres or SQL Server), the database and the user will remain untouched).{{% /alert %}}
532+
{{% alert color="info" %}}If the storage plan is using a JDBC plan (not Postgres or SQL Server), the database and the user will remain untouched.{{% /alert %}}
533533

534534
* Files related to that environment will be deleted from the S3/Minio storage bucket (or prefix if this is using a shared bucket).
535535

@@ -549,10 +549,10 @@ If any of these garbage collection steps fail, you will no longer see the enviro
549549

550550
##### Custom JVM Heap Memory
551551

552-
You only need to manually adjust JVM memory usage if the default settings aren't fully utilizing available memory. The JVM's memory usage must always remain below the total core resource memory to prevent application crashloops
552+
Adjust the JVM memory usage manually if the default settings are not fully utilizing available memory. The JVM's memory usage must always remain below the total core resource memory to prevent application crashloops.
553553
For more information, see [JVM Memory Tuning for Mendix on Kubernetes](/developerportal/deploy/private-cloud-jvm-memory-tuning/).
554554

555-
{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/ChangeJVMHeapMemory.png" class="no-border" >}}
555+
{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/change-jvm-heapmemory.png" class="no-border" >}}
556556

557557
##### Read-Only Root Filesystem
558558

content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ For information on the current status of deployment to Mendix on Kubernetes and
2020
* We have aligned resource plans with Public Cloud standards and continue to support legacy plans.
2121
* Added a warning clarifying that cross-cluster restores are not supported (this limitation already existed) and environments are only visible within the same cluster.
2222
* We have fixed an issue where replicas with unknown status showed as licensed.
23-
* We have fixed an issue where scheduled events were missing after pipeline deployment and API updates.(Ticket 270822)
23+
* We have fixed an issue where scheduled events were missing after pipeline deployment and API updates. (Ticket 270822)
2424
* We enhanced namespace and cluster invite emails to clearly identify the Mendix on Kubernetes portal as the sender, and updated the email notification messages accordingly.
2525

2626
### February 25, 2026

static/attachments/deployment/private-cloud/private-cloud-deploy/ChangeJVMHeapMemory.png renamed to static/attachments/deployment/private-cloud/private-cloud-deploy/change-jvm-heapmemory.png

File renamed without changes.
82.7 KB
Loading
Binary file not shown.

0 commit comments

Comments
 (0)