infra/otc-metadata
14
0
Fork 13
Code Issues 5 Pull Requests Packages Releases Wiki Activity

fixing wrong naming and placement for fg best-practise
All checks were successful
gl/check check status: success (7f8cc49007acbd5a4b1b0c297e7e58e5e755c0a7)
Details
gl/gate gate status: success (7f8cc49007acbd5a4b1b0c297e7e58e5e755c0a7)
Details

Browse Source
This commit is contained in:
vladimirhasko
2023-07-04 22:31:18 +00:00
parent 966e61c110
commit 7f8cc49007
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
otc_metadata/data/services.yaml
View File

@ -597,13 +597,13 @@ documents:
title: API Reference title: API Reference
type: api-ref type: api-ref
- environment: internal - environment: internal
html_location: docs/fg/best-practice html_location: docs/fg/best-practise
link: /function-graph/best-practice/ link: /function-graph/best-practise/
pdf_name: fg-best-practice pdf_name: fg-best-practise
rst_location: best-practice/source rst_location: doc/best-practise/source
service_type: fg service_type: fg
title: Best Practice title: Best Practise
type: best-practice type: best-practise
- environment: internal - environment: internal
html_location: docs/fg/dev html_location: docs/fg/dev
link: /function-graph/dev-guide/ link: /function-graph/dev-guide/