correct PR number and add a question

Author: mariuskimmina

20220403-ACME-TLS.md

@@ -1,8 +1,8 @@
-# Add ACME protocol support for certificate management with DNS
+# Add ACME protocol support for certificate management into TLS plugin 
 
 | Status        | Proposed       |
 :-------------- |:---------------------------------------------------- |
-| **RFC #**     | [12](https://github.com/coredns/rfc/pull/12) |
+| **RFC #**     | [13](https://github.com/coredns/rfc/pull/13) |
 | **Author(s)** | Marius Kimmina(@[mariuskimmina](https://github.com/mariuskimmina)) |
 | **Sponsor**   | Yong Tang (@[yongtang](https://github.com/yongtang)), Paul Greenberg (@[greenpau](https://github.com/greenpau)) |
 | **Updated**   | 2022-04-01                                       |
@@ -195,9 +195,9 @@ I will also be in contact with the mentors and hope to gather a lot of feedback
 
 ## Questions and Discussion Topics
 
-1. Do coredns have a domain for testing and development? 
-2. Can a CoreDNS plugin utilize the underlying Caddy server to solve the HTTP-01 Challenge - which means serving a file on port 80?
-3. For the DNS-01 Challenge, I would assume that CoreDNS will generally not be the authoritative DNS Server for the domain in question, thus, we would also use the API of a DNS Provider to solve this challenge, right?
+1. Can a CoreDNS plugin utilize the underlying Caddy server to solve the HTTP-01 Challenge - which means serving a file on port 80?
+2. For the DNS-01 Challenge, I would assume that CoreDNS will generally not be the authoritative DNS Server for the domain in question, thus, we would also use the API of a DNS Provider to solve this challenge, right?
+3. How should I configure the workers to look for the leader? When the certificate is renewed, how does the master know where the workers are and how to send the certificate to them?
 
 ## References