Skip to content
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.

Sign up for GitHub

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

fix link broken when tags were removed #128

Merged
merged 1 commit into from
Jul 26, 2024
Merged

fix link broken when tags were removed #128

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 0 additions & 1 deletion docs/community-events/20240221-Intro-to-TROLIE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,4 +162,3 @@ identified](https://github.com/trolie/spec/issues/43) to properly document this
feature.

[recap]: https://community.linuxfoundation.org/events/details/lfhq-lf-energy-presents-webinar-introduction-to-trolie
[patchForecast]: https://trolie.energy/spec#tag/Rating-Proposals/operation/patchRatingForecastProposalForProvider
4 changes: 2 additions & 2 deletions docs/example-narratives/submitting-forecasts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ APIs in particular ([background](../articles/trolie-for-ems-and-ot)).

If a Transmission Owner is their own Ratings Provider, they must regularly send
a Ratings Forecast to their Transmission Provider. TROLIE provides the
[patchRatingForecastProposal](../spec#tag/Rating-Proposals/operation/patchRatingForecastProposal)
[patchRatingForecastProposal](../spec#tag/Forecasting/operation/patchRatingForecastProposal)
operation for this purpose.


Expand Down Expand Up @@ -102,7 +102,7 @@ there are other client errors that are not tolerated, including:
* Unprocessable content error: when none of the individual resource Forecast
Proposals are valid, but the request is otherwise well-formed.

Additional client errors are identified in the [patchRatingForecastProposal spec](../spec#tag/Rating-Proposals/operation/patchRatingForecastProposal).
Additional client errors are identified in the [patchRatingForecastProposal spec](../spec#tag/Forecasting/operation/patchRatingForecastProposal).

### Clients Should Check the `incomplete-obligation-count`
{:.no_toc}
Expand Down
4 changes: 2 additions & 2 deletions docs/example-narratives/submitting-realtime-ratings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ on [forecast](submitting-forecasts) ratings may be helpful for background.

If a Transmission Owner is their own Ratings Provider, they must regularly send
real-time ratings to their Transmission Provider. TROLIE provides the
[postRealTimeProposal](../spec#tag/Rating-Proposals/operation/postRealTimeProposal)
[postRealTimeProposal](../spec#tag/Real-Time/operation/postRealTimeProposal)
operation for this purpose.


Expand Down Expand Up @@ -77,7 +77,7 @@ may also consider obligations for resources that would normally not have
their ratings submitted as TROLIE proposals, but rather through other means, such as ICCP.

Therefore, clients should rely more on asynchronous use of
[getRealTimeProposalStatus](../spec#tag/Rating-Proposals/operation/getRealTimeProposalStatus)
[getRealTimeProposalStatus](../spec#tag/Real-Time/operation/getRealTimeProposalStatus)
as a way to monitor whether the Clearinghouse considers their ongoing data stream
healthy.

Expand Down