Revise section headings for LSST integration (#11)

* Revise section headings for LSST integration

Updated section headings in resolver documentation to reflect changes from TNS/ZTF to TNS/LSST and SIMBAD/ZTF to SIMBAD/LSST.

* Correct source of alerts in livestream service documentation

Updated the description of the livestream service to reflect the correct source of alerts.

Author: emilleishida

docs/services/api/resolver.md

@@ -9,7 +9,7 @@ Instead of proposing a new naming scheme, we aim to provide a service that allow
 
 We are committed to expanding this service and will continue to add new sources of information.
 
-### TNS to ZTF
+### TNS to LSST
 
 Question: I have a TNS identifier, are there LSST `diaObjectId` corresponding?
 
@@ -59,7 +59,7 @@ pdf = pd.read_json(io.BytesIO(r.content)) # (1)!
     pdf = pd.read_json(io.BytesIO(r.content))
     ```
 
-### ZTF to TNS
+### LSST to TNS
 
 Question: I have a LSST `diaObjectId` name, are there counterparts in TNS?
 
@@ -82,7 +82,7 @@ r = requests.post(
 pdf = pd.read_json(io.BytesIO(r.content))
 ```
 
-### SIMBAD to ZTF
+### SIMBAD to LSST
 
 I have an astronomical object name referenced in SIMBAD, are there counterparts in LSST? As these objects can be extended, we typically provide coordinates, and then you need to run a conesearch:
 

docs/services/livestream.md

@@ -10,7 +10,7 @@ This manual has been tested for `fink-client` version 10.0. Other versions might
 
 ## Purpose
 
-The livestream service is based on the Fink filters. After each exposure, Fink processes the alerts sent by ZTF and the filters select alerts to be transmitted based on their content. These alerts are sent to the Fink [Apache Kafka :lucide-external-link:](https://kafka.apache.org/){target="blank_"} cluster, and substreams are produced (1 filter = 1 substream), identified by their _topic_ name. Each alert pushed is available 7 days in the queue, and consumers can replay streams indefinitely.
+The livestream service is based on the Fink filters. After each exposure, Fink processes the alerts sent by LSST and the filters select alerts to be transmitted based on their content. These alerts are sent to the Fink [Apache Kafka :lucide-external-link:](https://kafka.apache.org/){target="blank_"} cluster, and substreams are produced (1 filter = 1 substream), identified by their _topic_ name. Each alert pushed is available for 7 days in the queue, and consumers can replay streams indefinitely.
 
 As Kafka can be somehow cumbersome, we developed a client to facilitate the stream consuming part for Fink users: [fink-client :lucide-external-link:](https://github.com/astrolabsoftware/fink-client){target="blank_"}. Users can connect to one or more topics, and new topics can be created via new Fink filters.