From b7576b3b24e20c4ccb4d589c6f2fbbd65b83e045 Mon Sep 17 00:00:00 2001
From: Abit <abitmore@users.noreply.github.com>
Date: Wed, 19 Feb 2025 16:43:27 +0100
Subject: [PATCH] Update links in FAQ

---
 docs/faq.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/faq.rst b/docs/faq.rst
index abbee9d5..db416abc 100644
--- a/docs/faq.rst
+++ b/docs/faq.rst
@@ -27,10 +27,10 @@ Note: this way has limitation: public nodes doesn't store full account history,
 only limited number of entries
 
 * By querying `elasticsearch plugin
-  <https://dev.bitshares.works/en/master/supports_dev/elastic_search_plugin.html>`_.
+  <https://docs.bitshares.dev/en/master/supports_dev/elastic_search_plugin.html>`_.
   In short, elasticsearch plugin export account history data into elasticsearch
   instance, from which it's can be obtained directly or via elasticsearch
-  wrapper. See `<https://eswrapper.bitshares.eu/apidocs/>`_ to get info on how
+  wrapper. See `<https://api.bitshares.ws/docs>`_ to get info on how
   to query the wrapper. A real-world example of elasticsearch wrapper usage for
   obtaining filled orders history is `bitshares-tradehistory-analyzer
   </~https://github.com/bitfag/bitshares-tradehistory-analyzer>`_