Skip to content

Commit db1880d

Browse files
committed
address rosemary review comments
1 parent b4f4f32 commit db1880d

File tree

1 file changed

+4
-4
lines changed
  • docs-source/content/userguide/managing-domains/fmw-infra

1 file changed

+4
-4
lines changed

docs-source/content/userguide/managing-domains/fmw-infra/_index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -354,15 +354,15 @@ is provided that demonstrates how to create a FMW Infrastructure domain.
354354
There are two kind of patches that can be applied to the FMW Infrastructure binaries:
355355

356356
* Patches which are eligible for Zero Downtime Patching (ZDP), meaning that
357-
they can be applied in a rolling fashion.
358-
* non ZDP eligible compliant patches, meaning that the domain must be shutdown
357+
they can be applied with a rolling restart.
358+
* Non-ZDP eligible compliant patches, meaning that the domain must be shut down
359359
and restarted.
360360

361361
You can find out whether or not a patch is eligible for Zero Downtime Patching
362362
by consulting the README file that accompanies the patch.
363363

364-
If you wish to apply a ZDP compliant patch which can be applied in a rolling
365-
fashion, after you have patched the domain image as shown in this
364+
If you wish to apply a ZDP compliant patch which can be applied with a rolling
365+
restart, after you have patched the domain image as shown in this
366366
[sample](https://github.com/oracle/docker-images/tree/master/OracleFMWInfrastructure/samples/12213-patch),
367367
you can edit the domain custom resource with the name of the new image and
368368
the operator will initiate a rolling restart of the domain.

0 commit comments

Comments
 (0)