Developer doc: tiny typos

doc/developer/architecture.tex

@@ -190,7 +190,7 @@ documentation generated by \texttt{make doc} for that purpose.
 
 In \framac, plug-ins are program analysis or source-to-source
 transformations. The ones provided within \framac are in directory
-\texttt{src/$plugin\_name$}. Each plug-in is an extension point of \framac which
+\texttt{src/plugins/$plugin\_name$}. Each plug-in is an extension point of \framac which
 has to be registered through \texttt{Plugin.Register}\scodeidx{Plugin}{Register}
 (see Section~\ref{adv:plugin-services}). \framac allows plug-in collaborations:
 a plug-in $p$ can use a list of plug-ins $p_1$, \dots, $p_n$ and
@@ -271,7 +271,7 @@ with the \framac kernel or other plug-ins.
 
 Next, \framac provides predefined ways to visit the ASTs, in particular through
 object-oriented visitors defined in directory
-\texttt{src/kernel\_services/visitor} (see Section~\ref{adv:visitors}). 
+\texttt{src/kernel\_services/visitors} (see Section~\ref{adv:visitors}). 
 Some predefined analyzers, such as a multiple generic dataflow analysis
 are provided in directory \texttt{src/kernel\_services/analysis}, while some
 predefined program transformation, such as cloning a function, are provided in

doc/developer/tutorial.tex

@@ -472,7 +472,7 @@ file names, in the correct \ocaml build order.
 \codeidx{PLUGIN\_NAME}
 \makefileinput{./tutorial/hello/generated/makefile_multiple/Makefile}
 
-The three followoing files completely replace the \texttt{./hello\_world.ml}
+The three following files completely replace the \texttt{./hello\_world.ml}
 from the previous section. Modules are directly called by their name in the
 classical \ocaml way.