Skip to content

Commit

Permalink
Merge pull request #121 from zimeon/example-caption-fixes
Browse files Browse the repository at this point in the history
Fix a couple of captions
  • Loading branch information
sfolsom authored Oct 24, 2023
2 parents 56db03b + bdd087f commit b78496f
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/0.1/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -339,7 +339,7 @@ It is _RECOMMENDED_{:.strong-term} that change sets be published on a regular sc

_Change Sets_{:.term} _MUST_{:.strong-term} be implemented as an _OrderedCollectionPage_{:.term} following the definition in the Activity Stream specification. The key points are repeated here with examples specific to Entity Metadata Management.

#### Complete examples for a Change Set
#### Complete example for a Change Set

```json-doc
{
Expand Down Expand Up @@ -719,7 +719,7 @@ An entity that has been deprecated _SHOULD_{:.strong-term} have an [Entity Chang
* A `Deprecate` activity for the deprecated entity, and one or more `Create` activities for the replacement entity or entities.
In all cases, it is expected that the consumer will dereference the deprecated entity URI to obtain the updated entity description, including whether it was replaced.

#### Example Entity Change Activity exceprt for Deprecate in the Scenario where a Replacement Entity Already Exists
#### Example Entity Change Activity excerpt for Deprecate in the Scenario where a Replacement Entity Already Exists

```json-doc
{
Expand Down

0 comments on commit b78496f

Please sign in to comment.