From 13b0116ccc0d9cfeee393b5f74389d41180d7e05 Mon Sep 17 00:00:00 2001 From: Christopher Atkins Date: Fri, 26 Jul 2024 13:18:31 +0000 Subject: [PATCH] fix link broken when tags were removed --- docs/community-events/20240221-Intro-to-TROLIE.md | 1 - docs/example-narratives/submitting-forecasts.md | 4 ++-- docs/example-narratives/submitting-realtime-ratings.md | 4 ++-- 3 files changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/community-events/20240221-Intro-to-TROLIE.md b/docs/community-events/20240221-Intro-to-TROLIE.md index 88dd0cc..83052dd 100644 --- a/docs/community-events/20240221-Intro-to-TROLIE.md +++ b/docs/community-events/20240221-Intro-to-TROLIE.md @@ -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 diff --git a/docs/example-narratives/submitting-forecasts.md b/docs/example-narratives/submitting-forecasts.md index 20b4460..368a8be 100644 --- a/docs/example-narratives/submitting-forecasts.md +++ b/docs/example-narratives/submitting-forecasts.md @@ -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. @@ -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} diff --git a/docs/example-narratives/submitting-realtime-ratings.md b/docs/example-narratives/submitting-realtime-ratings.md index c242e80..731bfa0 100644 --- a/docs/example-narratives/submitting-realtime-ratings.md +++ b/docs/example-narratives/submitting-realtime-ratings.md @@ -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. @@ -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.