[flang-commits] [flang] 000eb1f - [docs][flang] Fix typos

[Sourabh Singh Tomar via flang-commits]

Author: SuJunda
Date: 2020-09-21T11:05:58+05:30
New Revision: 000eb1f314c1fc194454ad6c128f3c110eb8a34d

URL: https://github.com/llvm/llvm-project/commit/000eb1f314c1fc194454ad6c128f3c110eb8a34d
DIFF: https://github.com/llvm/llvm-project/commit/000eb1f314c1fc194454ad6c128f3c110eb8a34d.diff

LOG: [docs][flang] Fix typos

Reviewed By: SouraVX

Differential Revision: https://reviews.llvm.org/D87885

Added: 
    

Modified: 
    flang/docs/Calls.md

Removed: 
    


################################################################################
diff  --git a/flang/docs/Calls.md b/flang/docs/Calls.md
index 440d0bd147c2..cbf689f199ef 100644
--- a/flang/docs/Calls.md
+++ b/flang/docs/Calls.md
@@ -131,7 +131,7 @@ below; this is of course not standard terminology.
 Internal and module subprograms that are ever passed as arguments &/or
 assigned as targets of procedure pointers may be F77ish.
 
-Every F77ish procedure can and must be distiguished at compilation time.
+Every F77ish procedure can and must be distinguished at compilation time.
 Such procedures should respect the external naming conventions (when external)
 and any legacy ABI used for Fortran '77 programs on the target architecture,
 so that portable libraries can be compiled
@@ -157,7 +157,7 @@ internal procedures.
 Note that the `INTENT` attribute does not, by itself,
 require the use of explicit interface; neither does the use of a dummy
 procedure (implicit or explicit in their interfaces).
-So the analyis of calls to F77ish procedures must allow for the
+So the analysis of calls to F77ish procedures must allow for the
 invisible use of `INTENT(OUT)`.
 
 ## Protocol overview
@@ -485,7 +485,7 @@ type-bound procedure in the type corresponds to an index into this table.
 
 Calls to dummy procedures and procedure pointers that resolve to
 internal procedures need to pass an additional "host instance" argument that
-addresses a block of storage in the stack frame of the their
+addresses a block of storage in the stack frame of their
 host subprogram that was active at the time they were passed as an
 effective argument or associated with a procedure pointer.
 This is similar to a static link in implementations of programming