Sync docs

Signed-off-by: Kemal Akkoyun <kakkoyun@gmail.com>
parca-dev · Oct 7, 2021 · 14cc89c · 14cc89c
1 parent 252de71
commit 14cc89c
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/design.md b/docs/design.md
@@ -81,7 +81,7 @@ Kernel stack traces are immediately symbolized by the Parca Agent since the Kern
 
 Binaries or shared libraries/objects that contain debug symbols have their symbols extracted and uploaded to the remote server. The remote server can then use it to symbolize the stack traces at read time rather than in the agent. This also allows debug symbols to be uploaded separately if they are stripped in a CI process or retrieved from symbol servers such as [debuginfod](https://sourceware.org/elfutils/Debuginfod.html), [Microsoft symbol server](https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/microsoft-public-symbols), or [others](https://getsentry.github.io/symbolicator/).
 
-Future integrations of interpreted (eg. Ruby, nodejs, python) or JIT languages (eg. JVM) must resolve symbols to their pprof `Location` `Line`s and `Function`s directly in the agent and persisted in the pprof profile since their dynamic nature cannot be guarateed to be stable.
+Future integrations of interpreted (e.g. Ruby, nodejs, python) or JIT languages (e.g. JVM) must resolve symbols to their pprof `Location` `Line`s and `Function`s directly in the agent and persisted in the pprof profile since their dynamic nature cannot be guaranteed to be stable.
 
 ## Send data to server
 

diff --git a/docs/security.md b/docs/security.md
@@ -43,7 +43,7 @@ Parca Agent supply chain uses [Dependabot](https://docs.github.com/en/code-secur
 
 ## Report Security Vulnerabilities
 
-As with any complex system, it is near certain that bugs will be found, some of them security-relevant. If you find a security bug, please report it privately to the [parca-security@googlegroups.com](mailto:parca-security@googlegroups.com) mailing list. 
+As with any complex system, it is near certain that bugs will be found, some of them security-relevant. If you find a security bug, please report it privately to the [parca-security@googlegroups.com](mailto:parca-security@googlegroups.com) mailing list.
 We will fix the issue as soon as possible and coordinate a release date with you. You will be able to choose if you want public acknowledgement of your effort and if you want to be mentioned by name.
 
 Parca is maintained by volunteers, not by a company. Therefore, fixing security issues is done on a best-effort basis. We strive to release security fixes within 7 days.