proper command reference

README.md

@@ -37,7 +37,7 @@ Assuming you have a working protoc compiler on your system and have the existing
 
 The command should produce no output if successful. Additionally, the file */path/to/output/directory/google/protobuf/compiler/plugin_pb2.py* should have been created.
 
-Next, find the location of the installed protocol buffer Python package. If you have *locate*, try finding it via *`find descriptor_pb2.py`*. A common location is something like */usr/lib/python2.6/site-packages/protobuf-2.3.0-py2.6.egg/google/protobuf/*. Navigate to this directory and:
+Next, find the location of the installed protocol buffer Python package. If you have *locate*, try finding it via *`locate descriptor_pb2.py`*. A common location is something like */usr/lib/python2.6/site-packages/protobuf-2.3.0-py2.6.egg/google/protobuf/*. Navigate to this directory and:
 
     $ mkdir compiler
     $ touch compiler/__init__.py
@@ -63,4 +63,4 @@ The produced C++ code contains _extern "C" { }_ blocks around all code that util
 
 Windows requires an identifier for symbols to be exported from shared libraries. If compiling the lua-protobuf output to a shared library, you'll need to use a preprocessor define:
 
-    #define LUA_PROTOBUF_EXPORT __declspec(dllexport)
+    #define LUA_PROTOBUF_EXPORT __declspec(dllexport)