Updates the docs for clarity and correctness

Signed-off-by: Elena Kolevska <elena@kolevska.com>

Author: elena-kolevska

daprdocs/content/en/python-sdk-docs/python-client.md

@@ -39,7 +39,7 @@ with DaprClient() as d:
 ```
 
 #### Specifying an endpoint on initialisation:  
-When passed as an argument in the constructor, the endpoint takes precedence over any configuration or environment variable.
+When passed as an argument in the constructor, the gRPC endpoint takes precedence over any configuration or environment variable.
 
 ```python
 from dapr.clients import DaprClient
@@ -48,14 +48,13 @@ with DaprClient("mydomain:50051?tls=true") as d:
     # use the client
 ```  
 
-#### Specifying an endpoint in an environment variable:  
-You can use the standardised `DAPR_GRPC_ENDPOINT` and/or `DAPR_HTTP_ENDPOINT` environment variables to
-specify the endpoint. When these environment variables are set, the client can be initialised 
+#### Specifying the endpoint in an environment variable:  
+You can use the standardised `DAPR_GRPC_ENDPOINT` environment variable to
+specify the gRPC endpoint. When this variable is set, the client can be initialised 
 without any arguments:
 
 ```bash
 export DAPR_GRPC_ENDPOINT="mydomain:50051?tls=true"
-export DAPR_HTTP_ENDPOINT="https://mydomain:443"
 ```
 ```python
 from dapr.clients import DaprClient
@@ -65,7 +64,7 @@ with DaprClient() as d:
 ```  
 
 The legacy environment variables `DAPR_RUNTIME_HOST`, `DAPR_HTTP_PORT` and `DAPR_GRPC_PORT` are 
-also supported, but `DAPR_GRPC_ENDPOINT` and `DAPR_HTTP_ENDPOINT` take precedence.
+also supported, but `DAPR_GRPC_ENDPOINT` takes precedence.
 
 
 ## Building blocks