fix documentation typos (#7420)

Author: 0x6a62

fcs/docsrc/content/caches.fsx

@@ -9,7 +9,7 @@ This is a design note on the FSharpChecker component and its caches.  See also t
 Each FSharpChecker object maintains a set of caches.  These are
 
 * ``scriptClosureCache`` - an MRU cache of default size ``projectCacheSize`` that caches the 
-  computation of GetProjectOptionsFromScript. This computation can be lengthy as it can involve processing the transative closure
+  computation of GetProjectOptionsFromScript. This computation can be lengthy as it can involve processing the transitive closure
   of all ``#load`` directives, which in turn can mean parsing an unbounded number of script files
 
 * ``incrementalBuildersCache`` - an MRU cache of projects where a handle is being kept to their incremental checking state, 
@@ -50,7 +50,7 @@ The sizes of some of these caches can be adjusted by giving parameters to FSharp
 the cache sizes above indicate the "strong" size of the cache, where memory is held regardless of the memory 
 pressure on the system. Some of the caches can also hold "weak" references which can be collected at will by the GC.
 
-> Note: Because of these caches, uou should generally use one global, shared FSharpChecker for everything in an IDE application.
+> Note: Because of these caches, you should generally use one global, shared FSharpChecker for everything in an IDE application.
 
 
 Low-Memory Condition

fcs/docsrc/content/compiler.fsx

@@ -85,14 +85,14 @@ is not really an option.
 
 You still have to pass the "-o" option to name the output file, but the output file is not actually written to disk.
 
-The 'None' option indicates that the initiatlization code for the assembly is not executed. 
+The 'None' option indicates that the initialization code for the assembly is not executed. 
 *)
 let errors2, exitCode2, dynAssembly2 = 
     checker.CompileToDynamicAssembly([| "-o"; fn3; "-a"; fn2 |], execute=None)
      |> Async.RunSynchronously
 
 (*
-Passing 'Some' for the 'execute' parameter executes  the initiatlization code for the assembly.
+Passing 'Some' for the 'execute' parameter executes  the initialization code for the assembly.
 *)
 let errors3, exitCode3, dynAssembly3 = 
     checker.CompileToDynamicAssembly([| "-o"; fn3; "-a"; fn2 |], Some(stdout,stderr))

fcs/docsrc/content/editor.fsx

@@ -160,7 +160,7 @@ list of members of the string value `msg`.
 
 To do this, we call `GetDeclarationListInfo` with the location of the `.` symbol on the last line 
 (ending with `printfn "%s" msg.`). The offsets are one-based, so the location is `7, 23`.
-We also need to specify a function that says that the text has not changed and the current identifer
+We also need to specify a function that says that the text has not changed and the current identifier
 where we need to perform the completion.
 *)
 // Get declarations (autocomplete) for a location

fcs/docsrc/content/interactive.fsx

@@ -43,9 +43,9 @@ open System
 open System.IO
 open System.Text
 
-// Intialize output and input streams
-let sbOut = StringBuilder()
-let sbErr = StringBuilder()
+// Initialize output and input streams
+let sbOut = new StringBuilder()
+let sbErr = new StringBuilder()
 let inStream = new StringReader("")
 let outStream = new StringWriter(sbOut)
 let errStream = new StringWriter(sbErr)
@@ -121,7 +121,7 @@ result and an exception.
 
 The result part of ``EvalExpression`` and ``EvalExpressionNonThrowing`` is an optional ``FSharpValue``.
 If that value is not present then it just indicates that the expression didn't have a tangible
-result that could be represented as a .NET object.  This siutation shouldn't actually
+result that could be represented as a .NET object.  This situation shouldn't actually
 occur for any normal input expressions, and only for primitives used in libraries.
 *)
 
@@ -239,7 +239,7 @@ The 'fsi' object
 ------------------
 
 If you want your scripting code to be able to access the 'fsi' object, you should pass in an implementation of this object explicitly.
-Normally the one fromm FSharp.Compiler.Interactive.Settings.dll is used.
+Normally the one from FSharp.Compiler.Interactive.Settings.dll is used.
 *)
 
 let fsiConfig2 = FsiEvaluationSession.GetDefaultConfiguration(fsiSession)

fcs/docsrc/content/project.fsx

@@ -314,7 +314,7 @@ F# projects normally use the '.fsproj' project file format.
 A project cracking facility for legacy old-style .fsproj is provided as a separate NuGet package:
 FSharp.Compiler.Service.ProjectCracker. 
 
-Projecet cracking for modern project files should be done using a library such as DotNetProjInfo.
+Project cracking for modern project files should be done using a library such as DotNetProjInfo.
 See FsAutoComplete for example code.
 
 The legacy NuGet package `FSharp.Compiler.Service.ProjectCracker` contains a

fcs/docsrc/content/queue.fsx

@@ -36,7 +36,7 @@ These use cross-threaded access to the TAST data produced by other FSharpChecker
 Some tools throw a lot of interactive work at the FSharpChecker operations queue. 
 If you are writing such a component, consider running your project against a debug build
 of FSharp.Compiler.Service.dll to see the Trace.WriteInformation messages indicating the length of the
-operations queuea and the time to process requests.
+operations queue and the time to process requests.
 
 For those writing interactive editors which use FCS, you 
 should be cautious about operations that request a check of  the entire project.

fcs/docsrc/content/react.fsx

@@ -67,7 +67,7 @@ If your host happens to be Visual Studio, then this is one technique you can use
 
         ...
         
-        // Unadvise file changes...
+        // Unadvised file changes...
         Com.ThrowOnFailure0(vsFileWatch.UnadviseFileChange(cookie))
 
 

fcs/docsrc/content/symbols.fsx

@@ -101,7 +101,7 @@ Now get the value that corresponds to the function defined in the code:
 let fnVal = moduleEntity.MembersFunctionsAndValues.[0]
 
 (**
-Now look around at the properties describing the function value. All fo the following evaluate to `true`:
+Now look around at the properties describing the function value. All of the following evaluate to `true`:
 *)
 fnVal.Attributes.Count = 1
 fnVal.CurriedParameterGroups.Count // 1
@@ -178,9 +178,9 @@ for assembly in projectContext.GetReferencedAssemblies() do
 (**
 **Notes:**
 
-  - If incomplete code is present, some or all of the attirbutes may not be quite as expected.
+  - If incomplete code is present, some or all of the attributes may not be quite as expected.
   - If some assembly references are missing (which is actually very, very common), then 'IsUnresolved'  may
-    be true on values, members and/or entites related to external assemblies.  You should be sure to make your
+    be true on values, members and/or entities related to external assemblies.  You should be sure to make your
     code robust against IsUnresolved exceptions.
 
 *)

fcs/docsrc/content/tokenizer.fsx

@@ -49,7 +49,7 @@ on the `FSharpSourceTokenizer` object that we created earlier:
 let tokenizer = sourceTok.CreateLineTokenizer("let answer=42")
 (**
 Now, we can write a simple recursive function that calls `ScanToken` on the `tokenizer`
-until it returns `None` (indicating the end of line). When the function suceeds, it 
+until it returns `None` (indicating the end of line). When the function succeeds, it 
 returns `FSharpTokenInfo` object with all the interesting details:
 *)
 /// Tokenize a single line of F# code

fcs/docsrc/content/untypedtree.fsx

@@ -155,7 +155,7 @@ be another source of calls to `visitExpression`.
 ### Walking over declarations
 
 As mentioned earlier, the AST of a file contains a number of module or namespace declarations
-(top-level node) that contain declarations inside a module (let bindings or types) or inisde
+(top-level node) that contain declarations inside a module (let bindings or types) or inside
 a namespace (just types). The following functions walks over declarations - we ignore types,
 nested modules and all other elements and look only at top-level `let` bindings (values and 
 functions):