diff --git a/src/ifcblenderexport/Makefile b/src/ifcblenderexport/Makefile
index 65c79ccbac..a7ce8a5400 100644
--- a/src/ifcblenderexport/Makefile
+++ b/src/ifcblenderexport/Makefile
@@ -98,7 +98,7 @@ endif
 	# Provides IFCCSV functionality
 	cp -r dist/working/IfcOpenShell-0.6.0/src/ifccsv/* dist/blenderbim/libs/site/packages/
 	# Provides IFCPatch functionality
-	cp -r dist/working/IfcOpenShell-0.6.0/src/ifcpatch dist/blenderbim/libs/site/packages/
+	cp -r dist/working/IfcOpenShell-0.6.0/src/ifcpatch/ifcpatch dist/blenderbim/libs/site/packages/
 	rm -rf dist/working
 
 	# Provides Mustache templating in construction documentation
diff --git a/src/ifcpatch/README.md b/src/ifcpatch/README.md
index 7baafb9b35..bf26bcea88 100644
--- a/src/ifcpatch/README.md
+++ b/src/ifcpatch/README.md
@@ -49,8 +49,8 @@ optional arguments:
 Exactly how it is run depends on the recipe. A recipe may require zero or more
 arguments which are specific to the recipe. Here's an example which runs the
 `ExtractElements` recipe, which, as the same suggests, extracts out elements.
-This recipe expects one argument, which is a [filtering
-query](https://wiki.osarch.org/index.php?title=IfcOpenShell_code_examples#IFC_Query_Syntax).
+This recipe expects one argument, which uses the [IFC Query
+syntax](https://wiki.osarch.org/index.php?title=IfcOpenShell_code_examples#IFC_Query_Syntax).
 In this example, we'll extract out all `IfcWall` elements.
 
 ```
@@ -65,6 +65,7 @@ ifcpatch.execute({
     "input": "input.ifc",
     "output": "output.ifc",
     "recipe": "ExtractElements",
+    "log": "ifcpatch.log",
     "arguments": [".IfcWall"],
 })
 ```