[lld] Fix typos in documentation

[kazutakahirata]

No description provided.

[llvmbot]

@llvm/pr-subscribers-lld

Author: Kazu Hirata (kazutakahirata)

Changes

---

Full diff: https://github.com/llvm/llvm-project/pull/139854.diff

2 Files Affected:

• (modified) lld/docs/ELF/warn_backrefs.rst (+2-2)
• (modified) lld/docs/windows_support.rst (+1-1)

diff --git a/lld/docs/ELF/warn_backrefs.rst b/lld/docs/ELF/warn_backrefs.rst
index fac2145cc0c0e..bb9d86ce685c0 100644
--- a/lld/docs/ELF/warn_backrefs.rst
+++ b/lld/docs/ELF/warn_backrefs.rst
@@ -11,8 +11,8 @@ so far. When encountering an archive or an object file surrounded by
 symbol definitions; this may result in input files being loaded, updating the
 set of undefined symbol references. When all resolving definitions have been
 loaded from the archive, the linker moves on the next file and will not return
-to it.  This means that if an input file to the right of a archive cannot have
-an undefined symbol resolved by a archive to the left of it. For example:
+to it.  This means that if an input file to the right of an archive cannot have
+an undefined symbol resolved by an archive to the left of it. For example:
 
     ld def.a ref.o
 
diff --git a/lld/docs/windows_support.rst b/lld/docs/windows_support.rst
index e4640b4a5259a..38688a9629227 100644
--- a/lld/docs/windows_support.rst
+++ b/lld/docs/windows_support.rst
@@ -86,7 +86,7 @@ MSBuild.exe had been shipped as a component of the .NET framework, but since
 2013 it's part of Visual Studio. You can find it at "C:\\Program Files
 (x86)\\msbuild".
 
-You can build LLD as a 64 bit application. To do that, open VS2013 x64 command
+You can build LLD as a 64-bit application. To do that, open VS2013 x64 command
 prompt and run cmake for "Visual Studio 12 Win64" target.
 
 Using Ninja

[llvmbot]

@llvm/pr-subscribers-lld-elf

Author: Kazu Hirata (kazutakahirata)

Changes

---

Full diff: https://github.com/llvm/llvm-project/pull/139854.diff

2 Files Affected:

• (modified) lld/docs/ELF/warn_backrefs.rst (+2-2)
• (modified) lld/docs/windows_support.rst (+1-1)

diff --git a/lld/docs/ELF/warn_backrefs.rst b/lld/docs/ELF/warn_backrefs.rst
index fac2145cc0c0e..bb9d86ce685c0 100644
--- a/lld/docs/ELF/warn_backrefs.rst
+++ b/lld/docs/ELF/warn_backrefs.rst
@@ -11,8 +11,8 @@ so far. When encountering an archive or an object file surrounded by
 symbol definitions; this may result in input files being loaded, updating the
 set of undefined symbol references. When all resolving definitions have been
 loaded from the archive, the linker moves on the next file and will not return
-to it.  This means that if an input file to the right of a archive cannot have
-an undefined symbol resolved by a archive to the left of it. For example:
+to it.  This means that if an input file to the right of an archive cannot have
+an undefined symbol resolved by an archive to the left of it. For example:
 
     ld def.a ref.o
 
diff --git a/lld/docs/windows_support.rst b/lld/docs/windows_support.rst
index e4640b4a5259a..38688a9629227 100644
--- a/lld/docs/windows_support.rst
+++ b/lld/docs/windows_support.rst
@@ -86,7 +86,7 @@ MSBuild.exe had been shipped as a component of the .NET framework, but since
 2013 it's part of Visual Studio. You can find it at "C:\\Program Files
 (x86)\\msbuild".
 
-You can build LLD as a 64 bit application. To do that, open VS2013 x64 command
+You can build LLD as a 64-bit application. To do that, open VS2013 x64 command
 prompt and run cmake for "Visual Studio 12 Win64" target.
 
 Using Ninja