Updating Slack link

README.md

@@ -28,7 +28,7 @@
 
 <!-- Under the scope of the [AMD Xilinx University Program](https://www.xilinx.com/support/university/XUP-HACC.html), the Heterogeneous Accelerated Compute Clusters (HACCs) is a unique initiative to support novel research in adaptive compute acceleration for high-performance computing (HPC). The scope of the program is broad and encompasses systems, architecture, tools, and applications. HACCs are equipped with the latest Xilinx technology for adaptive compute acceleration. -->
 
-Under the scope of the <a href="https://www.xilinx.com/support/university/XUP-HACC.html">AMD University Program</a>, the <a href="https://www.amd-haccs.io">Heterogeneous Accelerated Compute Clusters (HACCs)</a> is a special initiative to support novel research in adaptive compute acceleration for high-performance computing (HPC). The scope of the program is broad and encompasses systems, architecture, tools, and applications. 
+Under the scope of the <a href="https://www.xilinx.com/support/university/XUP-HACC.html">AMD University Program,</a> the <a href="https://www.amd-haccs.io">Heterogeneous Accelerated Compute Clusters (HACCs)</a> is a special initiative to support novel research in adaptive compute acceleration for high-performance computing (HPC). The scope of the program is broad and encompasses systems, architecture, tools, and applications. 
 
 HACCs are equipped with the latest Xilinx hardware and software technologies for adaptive compute acceleration research. Each cluster is specially configured to enable some of the world’s foremost academic teams to conduct state-of-the-art HPC research. 
 
@@ -156,7 +156,7 @@ If you use this repository in your work, we kindly request that you cite it as f
     author = {Javier Moya, Matthias Gabathuler, Mario Ruiz, Gustavo Alonso},
     title = {{H}eterogeneous {A}ccelerated {C}ompute {C}luster - {ETH Zürich}},
     howpublished = {\url{https://github.com/fpgasystems/hacc}},
-    doi = {10.5281/zenodo.8340449}
+    doi = {10.5281/zenodo.8340449},
     year = {2022},
 }
 ```

docs/first-steps.md

@@ -17,9 +17,9 @@ Before continuing, please make sure you have been already accepted on ETH Züric
 ## Setting your passwords
 Once your ETH account has been created, you will need to generate two different passwords: an LDAP/Active directory password and a RADIUS password. The first one is part of your main ETH credentials; the *remote authentication dial-in user service (RADIUS)* password is used for [setting your remote secure access](#setting-your-remote-secure-access). Please, follow these steps to generate them:
 
-1. Visit the ETH Zürich [Web Center](https://iam.password.ethz.ch/authentication/login_en.html),
-2. Click on *Forgot your password* to receive a temporal password to use with [Web Center](https://iam.password.ethz.ch/authentication/login_en.html),
-3. Log in to [Web Center](https://iam.password.ethz.ch/authentication/login_en.html) and click on *Self service/Change password*,
+1. Visit the ETH Zürich [Web Center,](https://iam.password.ethz.ch/authentication/login_en.html)
+2. Click on *Forgot your password* to receive a temporal password to use with Web Center,
+3. Log in to Web Center and click on *Self service/Change password*,
 4. Select the *LDAPS* and *Active Directory* checkboxes and introduce your new password, and
 5. Select the *Radius* checkbox and introduce your new password.
 

docs/operating-the-cluster.md

@@ -17,7 +17,7 @@ The following figure shows a simplified model of HACC’s Ansible automation pla
 
 The playbooks defining our cluster are grouped into two categories: [IaaS](../docs/vocabulary.md#infrastructure-as-a-service-iaas) and [PaaS](../docs/vocabulary.md#platform-as-a-service-paas) playbooks. We refer the IaaS playbooks to the [YAML](../docs/vocabulary.md#yaml) files describing the infrastructure itself. This relates to the OS installation (including the definitions of partition sizes and similar lower-level attributes), virtual machines, networking setup, load balancers, connection topologies, and Debian package installation. With the PaaS playbooks, we take care of installing the software allowing users to develop their heterogeneous accelerated applications. 
 
-**Thanks to IaC and AAP, we can easily follow Xilinx’s tools versioning release schedule as mentioned in [Releases](../README.md#releases).**
+**Thanks to IaC and AAP, we can easily follow Xilinx’s tools versioning release schedule as mentioned in [Releases.](../README.md#releases)**
 
 <!-- The playbooks and task definning our cluster are grouped into two categories: IaaS and PaaS. We refer to the IaaS playbooks to those definning the infrastructure itself and related to the OS installation (including the definitions of partition sizes and similar lower-level attributes), networking setup, and Debian packages installation. With the PaaS playbooks we take care of the the software allowing our users to develop their heterogeneous accelerated applications, including XRT’s Xilinx Board Utility (xbutil), Xilinx tools (Vivado, Vitis_HLS, Vitis), the flashable partitions (or base shell) running on the FPGA, and any other sort of user tools we programed ourserlves. Thanks to Ansible we are able to easily follow Xilinx’s tools versioning release schedule as mentioned in [Releases](../README.md/#releases). -->
 

docs/technical-support.md

@@ -6,7 +6,7 @@
 
 # Technical support
 
-As mentioned [here,](https://www.xilinx.com/member/xup_research_clusters.html) we do not provide technical support and you should not use any of ETH’s emails with that purpose. Instead, please write to [research_clusters@amd.com](mailto:research_clusters@amd.com) or join the [HACC Slack workspace](https://join.slack.com/t/xaccworkspace/shared_invite/zt-o2xkrmj6-51z5BlI5WCBjwgpFXbO6Kw) to interact with other researchers. 
+As mentioned [here,](https://www.xilinx.com/member/xup_research_clusters.html) we do not provide technical support and you should not use any of ETH’s emails with that purpose. Instead, please write to [research_clusters@amd.com](mailto:research_clusters@amd.com) or join the [HACC Slack workspace](https://join.slack.com/t/amdhacc/shared_invite/zt-1kcx60g41-0PRQUtlpmw7CGeRfwxtyXA) to interact with other researchers. 
 
 ![HACC Slack workspace.](../imgs/slack.png "HACC Slack workspace.")
 *HACC Slack workspace.*

docs/vocabulary.md

@@ -43,13 +43,13 @@ Infrastructure as Code (IaC) is the process of provisioning and managing compute
 <!-- Infrastructure as code (IaC) uses [DevOps](#devops) methodology and versioning with a descriptive model to define and deploy infrastructure, such as networks, virtual machines, load balancers, and connection topologies. Just as the same source code always generates the same binary, an IaC model generates the same environment every time it deploys—specially when the source code is in a version control system. IaC is a key DevOps practice and a component of continuous delivery. With IaC, DevOps teams can work together with a unified set of practices and tools to deliver applications and their supporting infrastructure rapidly and reliably at scale. https://docs.microsoft.com/en-us/devops/deliver/what-is-infrastructure-as-code -->
 
 ### Tools
-There are many tools that fulfill infrastructure automation capabilities and use IaC. Broadly speaking, any framework or tool that performs changes or configures infrastructure declaratively or imperatively based on a programmatic approach can be considered IaC. ETHZ-HACC uses [Ansible](#ansible) for defining the cluster infrastructure.
+There are many tools that fulfill infrastructure automation capabilities and use IaC. Broadly speaking, any framework or tool that performs changes or configures infrastructure declaratively or imperatively based on a programmatic approach can be considered IaC. ETHZ-HACC uses [Ansible](#ansible-automation-platform-aap) for defining the cluster infrastructure.
 
 ### Relation to DevOps
 IaC can be a key attribute of enabling best practices in [DevOps](#devops)–developers become more involved in defining configuration and Ops teams get involved earlier in the development process. Tools that utilize IaC bring visibility to the state and configuration of servers and ultimately provide the visibility to users within the enterprise, aiming to bring teams together to maximize their efforts.
 
 ## Shape up
-Instead of *Scrum,* we use [Shape up](https://basecamp.com/shapeup) to shape and build our [Applications](./applications.md). To execute the techniques of the method we use [Basecamp](https://basecamp.com)—a project management tool that puts all our project communication, task management, and documentation in one place (where designers and programmers work seamlessly together). To see how we make that happen, please visit [How to implement Shape up in Basecamp](https://basecamp.com/shapeup/4.0-appendix-01).
+Instead of *Scrum,* we use [Shape up](https://basecamp.com/shapeup) to shape and build our accelerated applications. To execute the techniques of the method we use [Basecamp](https://basecamp.com)—a project management tool that puts all our project communication, task management, and documentation in one place (where designers and programmers work seamlessly together). To see how we make that happen, please visit [How to implement Shape up in Basecamp](https://basecamp.com/shapeup/4.0-appendix-01).
 
 ## Spine-leaf architecture 
 A spine-leaf architecture is data center network topology that consists of two switching layers—a spine and leaf. The leaf layer consists of access switches that aggregate traffic from servers and connect directly into the spine or network core. Spine switches interconnect all leaf switches in a full-mesh topology. <!-- https://www.arubanetworks.com/faq/what-is-spine-leaf-architecture/ -->