docs(redis): remove "fake" redis connection strings

Author: jslvtr

docs/docs/12_task_queues_emails/04_populate_rq_task_queue/README.md

@@ -76,10 +76,10 @@ def send_user_registration_email(email, username):
 Remember to change "Your Name" in `from` to whatever name you want your emails to come from!
 :::
 
-Next up, let's get our Redis connection string and add it to the `.env` file:
+Next up, add the Redis connection string that we got in the [previous section](../what_is_task_queue) to the `.env` file:
 
 ```text title=".env"
-REDIS_URL="rediss://red-ct8aen0hkl10:[email protected]:6379"
+REDIS_URL="<insert your Redis url here>"
 ```
 
 And then let's go to our User resource and add a couple of imports:

docs/docs/12_task_queues_emails/05_rq_background_worker/README.md

@@ -8,7 +8,7 @@ To do this, we'll run a background worker whose job it is to pop items off the q
 If you are using MacOS or Linux, you can run the background worker for testing using this command (make sure your virtual environment is active):
 
 ```bash
-rq worker -u rediss://red-ccu1t8a0hklj2a10:[email protected]:6379 emails
+rq worker -u <insert your Redis url here> emails
 ```
 
 The `rq` executable is available after installing the `rq` library with `pip`. The `-u` flag gives it the Redis URL to connect to. The `emails` at the end is the name of the queue that it should consume from. Make sure it matches the name of the queue you defined in `resources/user.py`.
@@ -42,13 +42,9 @@ docker build -t rest-apis-flask-smorest-rq .
 Then run a container, but instead of running the default entrypoint (defined by the `CMD` line in the `Dockerfile`), we'll tell it to run the `rq` program:
 
 ```bash
-docker run -w /app rest-apis-flask-smorest-rq sh -c "rq worker -u rediss://red-caenka10:[email protected]:6379 emails"
+docker run -w /app rest-apis-flask-smorest-rq sh -c "rq worker -u <insert your Redis url here> emails"
 ```
 
-:::info
-Make sure to enter your own Redis connection string in that command!
-:::
-
 This ensures one of the [considerations](https://python-rq.org/docs/#considerations-for-jobs) that the `rq` documentation suggests: that the worker and the work generator (our API) share _exactly_ the same source code.
 
 Run another Docker container for your API, and try to register!
@@ -68,7 +64,7 @@ docker run -p 5000:5000 rest-apis-flask-smorest-rq sh -c "flask run --host 0.0.0
 <TabItem value="worker" label="Run the background worker">
 
 ```bash
-docker run -w /app rest-apis-flask-smorest-rq sh -c "rq worker -u rediss://red-caenka10:[email protected]:6379 emails"
+docker run -w /app rest-apis-flask-smorest-rq sh -c "rq worker -u <insert your Redis url here> emails"
 ```
 
 :::info