Skip to content

Commit 08b696c

Browse files
committed
editorial + edit graphic to remove spelling squiggly
1 parent d283a0a commit 08b696c

5 files changed

+4
-12
lines changed

img/integration-stages.png

914 KB
Loading

odb-resource-defaults.html.md.erb

-4
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,6 @@ When you set default values for VMs and disk types, it helps you to select the r
1515
resources for on-demand service
1616
broker (ODB) services when you use on-demand plans.
1717

18-
<p class="note">
19-
<span class="note__title">Note</span>
20-
Tanzu Operations Manager 2.9 and later supports defining VM and disk type defaults and constraints.
21-
</p>
2218

2319
## <a id="defaults"></a>VM and Persistent disk types
2420

runtime-config.html.md.erb

+3-2
Original file line numberDiff line numberDiff line change
@@ -13,10 +13,10 @@ You can manage runtime configs in the following ways:
1313
+ Create a tile that only contains a runtime config. See [Create a Runtime Config-Only Tile](#config-only).
1414

1515
For more information about runtime configs, see
16-
[Director Runtime Config](https://bosh.io/docs/runtime-config.html).
16+
[Director Runtime Config](https://bosh.io/docs/runtime-config.html) in the BOSH documentation.
1717

1818
A runtime config is a section of the tile metadata that defines global deployment configurations.
19-
Tile authors can create tiles that only contain a runtime config or add a runtime config to
19+
Tile authors can create tiles that contain only a runtime config or they can add a runtime config to
2020
an existing product tile. When a tile author includes a runtime config as a top-level property in the
2121
tile metadata, BOSH applies the runtime config to every VM in the deployment.
2222

@@ -32,6 +32,7 @@ The identifier follows the following format:
3232
```
3333
TILE_NAME-GUID-RUNTIME_CONFIG_NAME
3434
```
35+
3536
## <a id="create"></a>Add a runtime config
3637

3738
Tile authors can add `runtime_configs` as a top-level property in tile metadata. In the runtime config

tile-basics.html.md.erb

-5
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,3 @@ The service broker works by providing an API which the Cloud Controller calls to
1414
In addition to providing an API, a service broker publishes a service catalog that might include multiple service plans, such as a free tier and a metered tier. Brokers register their service plans with the Cloud Controller to populate the Marketplace, which developers access with `cf marketplace` or through Apps Manager.
1515

1616
Cloud operators make software services available to developers by finding them on [VMware Tanzu Network](https://network.tanzu.vmware.com/) and then installing and configuring them through a tile interface in the Tanzu Operations Manager **Installation Dashboard**. Installing a service tile creates a service broker, registers it with the Cloud Controller, and publishes the service plans that the broker offers. Developers can then create service instances in their spaces and bind them to their apps.
17-
18-
See the following:
19-
20-
* [How <%= vars.app_runtime_abbr %> and <%= vars.platform_name %> services work](cf-concepts.html).
21-
* [How tiles work](tile-structure.html).

tile-index.html.md.erb

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Tile References
33
owner: Services
44
---
55

6-
Here is some references that provide basic information about tiles:
6+
Here are some references that provide basic information about tiles:
77

88
* [Tile basics](/docs-tiledev/tile-basics.html)
99
* [How <%= vars.app_runtime_abbr %> and <%= vars.ops_manager %> services work](/docs-tiledev/cf-concepts.html)

0 commit comments

Comments
 (0)