Skip to content

[enterprise-4.2] Fix style for options that are not compulsory #22183

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 15, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion modules/migration-running-migration-plan-cam.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ You can run *Stage* multiple times to reduce the actual migration time.
+
*Migrate* stops the application workload on the source cluster and recreates its resources on the target cluster.

. Optionally, in the *Migrate* window, you can select *Do not stop applications on the source cluster during migration*.
. Optional: In the *Migrate* window, you can select *Do not stop applications on the source cluster during migration*.
. Click *Migrate*.
. When the migration is complete, verify that the application migrated successfully in the {product-title} 4.2 web console:

Expand Down
2 changes: 1 addition & 1 deletion modules/nw-egressnetworkpolicy-edit.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ To edit an existing egress network policy object for a project, complete the fol
$ oc get -n <project> egressnetworkpolicy
----

. Optionally, if you did not save a copy of the EgressNetworkPolicy object when you created the egress network firewall, enter the following command to create a copy.
. Optional: If you did not save a copy of the EgressNetworkPolicy object when you created the egress network firewall, enter the following command to create a copy.
+
----
$ oc get -n <project> \ <1>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ You can create a project using the *Developer* perspective, as follows:
image::odc_create_project.png[Create Project]

. In the *Create Project* dialog box, enter a unique name for the *Name* field. For example, enter `myproject` as the name of the project in the *Name* field.
. Optionally, add the *Display Name* and *Description* details for the Project.
. Optional: Add the *Display Name* and *Description* details for the Project.
. Click *Create*.

Your project is now created and you can add applications and other workloads in to this project.
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Create, build, and deploy an application on {product-title} using an existing co
image::odc_import_from_git.png[Import from Git]

. In the *Git* section, enter the Git repository URL for the codebase you want to use to create an application. For example, enter the URL of this sample nodejs application `\https://github.com/sclorg/nodejs-ex`.
. Optionally, you can click *Show Advanced Git Options* to add details such as:
. Optional: You can click *Show Advanced Git Options* to add details such as:

* *Git Reference* to point to code in a specific branch, tag, or commit to be used to build the application.
* *Context Dir* to specify the subdirectory for the application source code you want to use to build the application.
Expand All @@ -40,7 +40,7 @@ The *Serverless* section is displayed in the *Import from git* form only if the
====

. In the *Advanced Options* section, the *Create a route to the application* is selected by default so that you can access your application using a publicly available URL. You can clear the check box if you do not want to expose your application on a public route.
. Optionally, you can use the following advanced options to further customize your application:
. Optional: You can use the following advanced options to further customize your application:

Routing::
Click the *Routing* link to:
Expand Down