Merge pull request #81 from nikagar4epm/chore/readme_grammar_fixes

chore: updated Readme

Author: SolaWing

Readme.md

@@ -1,52 +1,52 @@
 # Xcode-Build-Server
 
-apple's [sourcekit-lsp](https://github.com/apple/sourcekit-lsp) doesn't support xcode project. but I found it provide a [build server protocol](https://build-server-protocol.github.io/docs/specification.html) to integrate with other build system. this is why I created this repo.
+Apple's [sourcekit-lsp](https://github.com/apple/sourcekit-lsp) doesn't support xcode project. But I found it provides a [build server protocol](https://build-server-protocol.github.io/docs/specification.html) to integrate with other build system. This is why I created this repo.
 
-This repo aims to integrate xcode with sourcekit-lsp, support all languages(swift, c, cpp, objc, objcpp) xcode supports, so I can develop iOS with my favorate editor.
+This repo aims to integrate xcode with sourcekit-lsp and support all the languages (swift, c, cpp, objc, objcpp) xcode supports, so I can develop iOS with my favorate editor.
 
 # Install
 
-this repo require Python3.9. The latest macos already contains this tool.
+This repo requires Python 3.9. The latest macOS already comes with this tool.
 
-then just clone this repo, and `ln -s ABSPATH/TO/xcode-build-server /usr/local/bin`
+After you've made sure you have Python 3.9, just clone this repo, and add a symbolic link to your bin folder by running: `ln -s ABSPATH/TO/xcode-build-server /usr/local/bin`
 
-here is script for quick install if your terminal cd to the dir you what save this repo:
+Here is a script for quick install if your working directory is your desired destination for the installation:
 
 `git clone "[email protected]:SolaWing/xcode-build-server.git" && ln -s "$PWD"/xcode-build-server/xcode-build-server /usr/local/bin`
 
 or
 
 `git clone "https://github.com/SolaWing/xcode-build-server.git" && ln -s "$PWD"/xcode-build-server/xcode-build-server /usr/local/bin`
 
-or install from brew
+or install using homebrew
 
 `brew install xcode-build-server`
 
-or install from [Macports](https://github.com/macports/macports-ports/blob/master/devel/xcode-build-server/Portfile):
+or install using [Macports](https://github.com/macports/macports-ports/blob/master/devel/xcode-build-server/Portfile):
 
 `sudo port install xcode-build-server`
 
 # Usage
 
-choose one of the following usage. No matter which method you use, you need to ensure that the directory where `buildServer.json` is located is **the root directory** of lsp
+Choose one of the following methods. (No matter which method you use, you need to ensure that the directory where `buildServer.json` is created in is **the root/working directory** of the LSP)
 
 ### Bind to Xcode
 Go to your workspace directory and execute one of the following commands:
 
 ```bash
-# *.xcworkspace or *.xcodeproj should be unique. can be omit and will auto choose the unique workspace or project.
-# -scheme can also be omit to auto bind the latest scheme build result. even change it in xcode after the buildServer.json generated
+# *.xcworkspace or *.xcodeproj should be unique. This can be omitted and the build server will automatically choose the unique workspace or project.
+# -scheme can also be omitted to automatically bind the latest scheme build result. even change it in xcode after the buildServer.json generated
 xcode-build-server config -workspace *.xcworkspace -scheme <XXX> 
 xcode-build-server config -project *.xcodeproj -scheme <XXX> 
 ```
 
 This will create or update the `buildServer.json` file, with a `kind: xcode` key, which instructs xcode-build-server to watch and use compile flags from the newest xcode build log.
 
-After this, you can open your file with sourcekit-lsp enabled, and it should works.
+After this, you can open your file with sourcekit-lsp enabled and it should work.
 
 If your compile info is outdated and something is not working properly, just build in xcode to refresh compile flags.
 
-> PS: xcodebuild can generate same build log as xcode, if you don't overwrite build dir and specify a -resultBundlePath. this way you don't have to open xcode to build. eg:
+> PS: xcodebuild can generate same build log as xcode if you don't overwrite build dir and specify a -resultBundlePath. This way you don't have to open xcode to build. eg:
 ```bash
 rm .bundle; xcodebuild -workspace *.xcworkspace -scheme <XXX> -destination 'generic/platform=iOS Simulator' -resultBundlePath .bundle build
 ```
@@ -65,41 +65,41 @@ this will parse the log, save compile info in a `.compile` file, and update `bui
 
 `<build_log_file>` can be created by redirecting `xcodebuild build` output to a file, or exported from xcode's build log UI.
 
-`<cmd generate build log>` will usually be xcodebuild, or `pbpaste` if copy from xcode's build log. for example:
+`<cmd generate build log>` will usually be xcodebuild, or `pbpaste` if copied from xcode's build log. for example:
 
 ```base
 xcodebuild -workspace *.xcworkspace -scheme <XXX> -configuration Debug build | xcode-build-server parse [-a]
 
 pbpaste | xcode-build-server parse [-a]
 ```
 
-When running for the first time, **you need to ensure that the log is complete**, otherwise some files cannot obtain the correct flags.
+When running for the first time, **you need to ensure that the log is complete**, otherwise some files won't be able to obtain correct flags.
 
 After completing these steps, restart your language server, and it should work as expected.
 
-if your build environment changes(eg: add new files, switch sdk, toggle debug/release, conditional macro, etc..) and your language server stops working, just repeat the previous steps to update the compile info. In these incremental update cases, **you should make sure to use the `-a` flag**, which will only add new flags, and other irrelevant old flags will remain unchanged.
+If your build environment changes(eg: add new files, switch sdk, toggle debug/release, conditional macro, etc..) and your language server stops working, just repeat the previous steps to update the compile info. In these incremental update cases, **you should make sure to use the `-a` flag**, which will only add new flags, and other irrelevant old flags will remain unchanged.
 
 if you use xcodebuild and want to see raw output, currently you can use the following commands: `xcodebuild ... | tee build.log; xcode-build-server parse -a build.log >/dev/null 2>&1`
 
 ### [Deprecated] Sync Xcodebuild log
-> this usage is deprecated by `bind xcodeproj`, which just a command and won't pollute your xcodeproj's config.  
-> switch from this usage to `bind xcodeproj`, you'll need to delete the `post-build-action` first. Otherwise, bind may not work properly. since kind will change to manual by post-build-action.
+> this usage is deprecated by `bind xcodeproj`, which is just a command and won't pollute your xcodeproj's config.  
+> switch from this usage to `bind xcodeproj`, you'll need to delete the `post-build-action` first. Otherwise, bind may not work properly. Since kind will change to manual by post-build-action.
 
 xcode-build-server provider `post-build-action` script to auto parse newest log into .compile and generate `buildServer.json`.  
 just add `xcode-build-server postaction | bash &` into script in **scheme -> Build -> Post-actions**. and script should choose provide build settings from target
 <img width="918" alt="图片" src="https://user-images.githubusercontent.com/3897953/178139213-cb655340-28f6-49f6-8e7d-666bb29e664f.png">
 
-after this, the compile info should auto generate when xcode build and no need further manual parse.
+after this, the compile info should auto generate when xcode builds and no need for further manual parsing.
 
 ## Indexing While Building
-[sourcekit-lsp](https://github.com/apple/sourcekit-lsp#indexing-while-building) use indexing while build.
-if you found find definition or references is not work correctly, just build it to update index
+[sourcekit-lsp](https://github.com/apple/sourcekit-lsp#indexing-while-building) uses indexing while building.
+If you find that find definitions or references are not working correctly, just build it to update index
 
 # More
 
-current implementation is basicly work, but may have some rough edges. Please report issue if you have any problem. If you want to help, can check the open issue list. PR is always welcome.
+Current implementation is basicly working, but may have some rough edges. Please report issue if you have any problem. If you want to help, you can check the open issue list. PR's are always welcome.
 
-when reporting an issue, you may provide your buildServer.json and run LSP with the environment variable SOURCEKIT_LOGGING=3 to provide detailed logs to help locate the problem.
+When reporting an issue, you may provide your buildServer.json and run LSP with the environment variable SOURCEKIT_LOGGING=3 to provide detailed logs to help locate the problem.
 
 # Common Issues