fix: regenerated client

Author: martynia

diracx-client/src/diracx/client/_generated/aio/operations/_operations.py

@@ -380,7 +380,7 @@ async def do_device_flow(self, *, user_code: str, **kwargs: Any) -> Any:
     async def finish_device_flow(self, *, code: str, state: str, **kwargs: Any) -> Any:
         """Finish Device Flow.
 
-        This the url callbacked by IAM/Checkin after the authorization
+        This the url callbacked by IAM/CheckIn after the authorization
         flow was granted.
         It gets us the code we need for the authorization flow, and we
         can map it to the corresponding device flow using the user_code

diracx-client/src/diracx/client/_generated/operations/_operations.py

@@ -980,7 +980,7 @@ def do_device_flow(self, *, user_code: str, **kwargs: Any) -> Any:
     def finish_device_flow(self, *, code: str, state: str, **kwargs: Any) -> Any:
         """Finish Device Flow.
 
-        This the url callbacked by IAM/Checkin after the authorization
+        This the url callbacked by IAM/CheckIn after the authorization
         flow was granted.
         It gets us the code we need for the authorization flow, and we
         can map it to the corresponding device flow using the user_code

docs/OPENTELEMETRY.md

@@ -2,8 +2,8 @@
 
 > :warning: **Experimental**: opentelemetry is an evolving product, and so is our implementation of it.
 
-``diracx`` is capable of sending [OpenTelemetry](https://opentelemetry.io/) data to a collector. The settings are controlled by the
-``diracx.routers.otel.OTELSettings`` classes
+`diracx` is capable of sending [OpenTelemetry](https://opentelemetry.io/) data to a collector. The settings are controlled by the
+`diracx.routers.otel.OTELSettings` classes
 `diracx` will then export metrics, traces, and logs. For the moment, nothing is really instrumented, but the infrastructure is there
 
 ![OTEL Logs](./otel-logs.png)

extensions/README.md

@@ -205,7 +205,7 @@ Note that even if you have your own `testing` package depending on `diracx-testi
 
 Working on this test extension is tricky as it is a subdirectory. if you want to debug it you need to:
 
-- buid the `gubbins` docker images (or download an art)
+- build the `gubbins` docker images (or download an art)
 - copy the files somewhere else
 - edit the pyproject
 - run_demo

extensions/gubbins/gubbins-client/src/gubbins/client/_generated/aio/operations/_operations.py

@@ -387,7 +387,7 @@ async def do_device_flow(self, *, user_code: str, **kwargs: Any) -> Any:
     async def finish_device_flow(self, *, code: str, state: str, **kwargs: Any) -> Any:
         """Finish Device Flow.
 
-        This the url callbacked by IAM/Checkin after the authorization
+        This the url callbacked by IAM/CheckIn after the authorization
         flow was granted.
         It gets us the code we need for the authorization flow, and we
         can map it to the corresponding device flow using the user_code

extensions/gubbins/gubbins-client/src/gubbins/client/_generated/operations/_operations.py

@@ -1033,7 +1033,7 @@ def do_device_flow(self, *, user_code: str, **kwargs: Any) -> Any:
     def finish_device_flow(self, *, code: str, state: str, **kwargs: Any) -> Any:
         """Finish Device Flow.
 
-        This the url callbacked by IAM/Checkin after the authorization
+        This the url callbacked by IAM/CheckIn after the authorization
         flow was granted.
         It gets us the code we need for the authorization flow, and we
         can map it to the corresponding device flow using the user_code