Had left a couple of references to proxies in the docs

JamesRandall · Mar 15, 2019 · b8eaa7f · b8eaa7f
1 parent 8cce1ca
commit b8eaa7f
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 5 deletions.
diff --git a/docfx/faq.md b/docfx/faq.md
@@ -12,10 +12,6 @@ Aim is to move it out of preview when Azure Functions v2 go to GA. Certainly won
 
 I'm still investigating this but there looks to be a bug in the cold start behaviour in Azure. The logs show the proxies are not always routed on to Functions and instead the funciton host looks for physical files. I have a GitHub issue raised which hopefully will help me gain more insight.
 
-## I get the error "Error processing configuration of Function Proxies"
-
-There used to be a requirement for a variable called ProxyPrefix which if missed would generate this error. Its no longer required so if you update to the latest version of the package that should resolve things.
-
 ## Are Pull Requests welcome?
 
 Heck yes. But if you're planning a major piece of work probably makes sense to have a conversation first. I'd hate to have folks waste their time.

diff --git a/docfx/guides/gettingStarted.md b/docfx/guides/gettingStarted.md
@@ -76,7 +76,7 @@ Ok. We can now run the project! If you do so you should see the Azure Function h
 
         HelloWorld: http://localhost:7071/v1/HelloWorld
 
-One of those is our underlying function and the other the proxy. If you open up your browser and enter the URL:
+If you open up your browser and enter the URL:
 
     http://localhost:7071/v1/HelloWorld