Replaced references to LiQui|> with Q#

NEWPROPOSAL/FULLPROP.tex

@@ -164,7 +164,7 @@ Describe the specific objectives of the project, which should be clear, measurab
 \label{sec:context}
 
 High-level programming languages (HLLs) increase programmer productivity and software reliability --- provided that the HLL compiler can generate machine code which runs well on the intended hardware platform. 
-Quantum algorithm designers have the choice of several powerful quantum programming languages~\cite{Alexander-S.-Green:2013fk, Paykin2017a, Steiger2016ProjectQ:-An-Op, export:209634}.
+Quantum algorithm designers have the choice of several powerful quantum programming languages~\cite{Alexander-S.-Green:2013fk, Paykin2017a, Steiger2016ProjectQ:-An-Op, qsharp}.
 \newt{%
   However, these languages do not describe how to realise programs on specific hardware platforms, of which there are several, using different technologies (ion traps, superconducting circuits, optics) and architectural concepts (networked vs.\ hybrid, ancilla driven, measurement based)~\cite{PhysRevX.4.041041,Raussendorf-2001,KendonAncilla}.
   Even at such a time as quantum hardware technology matures, we cannot be assured that exactly one platform will predominate for all quantum information processing applications.
@@ -615,8 +615,8 @@ various themes: the relation between \zx and other quantum computing representat
 \label{sec:progr-lang-supp}
 
 \oldt{In the quantum setting, several powerful high-level languages
-(HLLs) such as Quipper~\cite{Alexander-S.-Green:2013fk} and \liquid
-\cite{export:209634} have been proposed.  As in the case of their
+(HLLs) such as Quipper~\cite{Alexander-S.-Green:2013fk} and Q\#
+\cite{qsharp} have been proposed.  As in the case of their
 classical counterparts, these HLLs are not designed to be run directly
 on quantum hardware, rather their compilers typically output quantum
 circuit descriptions.
@@ -636,7 +636,7 @@ QASM~\cite{Cross2017Open-Quantum-As} in
 virtually any extant quantum HLL, albeit rather naively.
 Later, we will perform concrete front-end experiments using more
 sophisticated existing HLLs, for example \emph{Quipper},
-\liquid, or ProjectQ \cite{Steiger2016ProjectQ:-An-Op} during the
+Q\#~\cite{qsharp}, or ProjectQ \cite{Steiger2016ProjectQ:-An-Op} during the
 long running task~\ref{task:transHLL}.  
 
 This work package consists of a back-and-forth interaction between

NEWPROPOSAL/preamble.tex

@@ -24,6 +24,8 @@
 \def\e{\end{color}\xspace}
 \newcommand{\TODOb}[1]{\marginpar{\scriptsize\bB \textbf{TODO:} #1\e}}
 \newcommand{\oldt}[1]{{\color{blue} #1}}
+\newcommand{\newt}[1]{{\color{blue!50!red} #1}}
+
 
 % typographical improvements
 \usepackage[T1]{fontenc}
@@ -272,8 +274,8 @@
 
 \newcommand{\zx}{\textsc{zx}\xspace}
 \newcommand{\zxcalculus}{\textsc{zx}-calculus\xspace}
-\newcommand{\azx}{\textsc{azx}\xspace}
-\newcommand{\liquid}{LIQUi$\ket{}$\xspace}
+\newcommand{\azx}{\texttt{\bfseries\color{red!70!black} [REDEFINE \textbackslash azx MACRO]}\xspace}
+\newcommand{\liquid}{\texttt{\bfseries\color{red!70!black} [CONSIDER REPLACING REFERENCE TO LIQUID BY Q\#]}\xspace}
 
 \usepackage{pgfgantt}